After database restart we must restart also application server
Hello,
at our company we are using Pega 7.1.9 and Oracle Database 11g Enterprise Edition Release Proprietary information hidden.0 - 64bit Production.
After restarting Oracle DB we are also forced to reboot application server because Pega after databsae restart is unable to reestablish the connections.
At log im able to see:
Hello,
at our company we are using Pega 7.1.9 and Oracle Database 11g Enterprise Edition Release Proprietary information hidden.0 - 64bit Production.
After restarting Oracle DB we are also forced to reboot application server because Pega after databsae restart is unable to reestablish the connections.
At log im able to see:
"
11:11:44,424 INFO [stdout] (Dispatcher-Thread-99) Caused by SQL Problems.
11:11:44,424 INFO [stdout] (Dispatcher-Thread-99) Problem #1, SQLState 08003, Error code 17008: java.sql.SQLRecoverableException: Closed Connection
11:11:44,424 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:256)
11:11:44,425 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.Opener.openData(Opener.java:785)
11:11:44,425 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:4091)
11:11:44,425 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:3800)
11:11:44,426 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:3768)
11:11:44,426 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.lockInboxInner(EmailListener.java:2909)
11:11:44,427 INFO [stdout] (Dispatcher-Thread-99) at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
11:11:44,427 INFO [stdout] (Dispatcher-Thread-99) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
11:11:44,427 INFO [stdout] (Dispatcher-Thread-99) at java.lang.reflect.Method.invoke(Method.java:606)
11:11:44,428 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1270)
11:11:44,428 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1008)
11:11:44,429 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:874)
11:11:44,429 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.lockInbox(EmailListener.java:2858)
11:11:44,429 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.oneIteration(EmailListener.java:2754)
11:11:44,430 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.integration.engine.internal.services.email.EmailListener.run_(EmailListener.java:2644)
11:11:44,430 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:453)
11:11:44,431 INFO [stdout] (Dispatcher-Thread-99) at java.lang.Thread.run(Thread.java:745)
11:11:44,431 INFO [stdout] (Dispatcher-Thread-99) Caused by: java.sql.SQLRecoverableException: Closed Connection
11:11:44,432 INFO [stdout] (Dispatcher-Thread-99) at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3587)
11:11:44,432 INFO [stdout] (Dispatcher-Thread-99) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:744)
11:11:44,433 INFO [stdout] (Dispatcher-Thread-99) at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:730)
11:11:44,433 INFO [stdout] (Dispatcher-Thread-99) at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405)
11:11:44,434 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.prepareStatement(DatabaseConnectionImpl.java:575)
11:11:44,434 INFO [stdout] (Dispatcher-Thread-99) at com.pega.pegarules.data.internal.access.Opener.openData(Opener.java:692)"
Any hints please?
***Updated by moderator: Lochan to add Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Hi David,
I have raised an enhancement on your behalf and sent you a message with the details.
Hope to see you around the Community!
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US
I am pretty sure that app server restart is required after db restart. Not everthing is going to recover automatically after db restart. An enhancement request is recommended if not already.
Accepted Solution
Pegasystems Inc.
IN
Hi David,
I have raised an enhancement on your behalf and sent you a message with the details.
Hope to see you around the Community!
Lochan | Community Moderator | Pegasystems Inc.
Pega Systems
IN
do we have any update on this enhancement? Do we have a hotfix in place for this?
WE are landing into the same issue. And how do we handle this in Production? We expect the app server restarted after a DB restart everytime in Production env too?
Pegasystems Inc.
IN
Hello!
I have updated the Related Support Case Number field to reflect the enhancement request raised. Since you are a Pega employee, you would have the access to check that in our internal portal PMF to find out the status.
Pegasystems Inc.
IN
Hi Abu,
I do not see any updates for this enhancement request on our internal portal. Please check for the same with your Pega Account Executive who might obtain more information for you!
Regards,