Pega 8.4 application fails to restart in openshift
Hi PEGA Team,
Our PEGA applications are failing to restart in a particular Openshift cluster. If we move the application to a different cluster it works fine.
The problematic cluster is where our DEV/TEST app instances run. Hence our development activity is blocked due to this issue. Appreciate your help.
For some reason, the PEGA applications in DEV cluster throws the below exception during startup and fails to proceed.
1. I don’t see any issue in establishing TCPS connection to the DB.
2. We ran a java client program inside the PEGA Universal pod to query the DB with the same connection string as is configured in the PEGA app and it returned the exact result we were expecting.
3. The logs stop for about 90s (think this is the socketTimeout value set in JDBC_CONNECTION_PROPERTIES=socketTimeout=90) before the exception appears.
4. I tried to enable DEBUG logs in prlog4j2.xml, but couldn’t figure out which classes to monitor.
Anyone has any pointers? Please let us know.
21-Sep-2020 09:07:12.365 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: PEGA_DATA
21-Sep-2020 09:07:12.641 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0 ]
21-Sep-2020 09:07:12.641 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null
21-Sep-2020 09:07:12.642 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: PEGA_RULES
21-Sep-2020 09:07:12.643 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: PEGA_RULES
21-Sep-2020 09:07:12.643 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings
21-Sep-2020 09:07:12.681 INFO [main] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 08-04-01). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.
21-Sep-2020 09:07:12.684 INFO [main] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:08-04-01
21-Sep-2020 09:07:13.815 INFO [main] com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl. Using PRAppLoader implementation class: com.pega.pegarules.bootstrap.loader.PRAppLoader
We found that socket timeouts were occurring due to network issues in connecting to the Oracle DB. The tomcat context.xml had "connectionProperties=socketTimeout=90" setting. This was timing out due to the network problem.