Support Article
Execution of data flow fails with DatabaseException post upgrade
SA-63119
Summary
Execution of data flow fails with DatabaseException after upgrade to Pega 7.4.
Error Messages
[charlatan-watcher:20] [ STANDARD] [ ] [ ] (internal.jdbc.ExceptionWrapper) ERROR - Datasource: { "dataSource": "java:comp/env/jdbc/PegaRULES"}
[charlatan-watcher:20] [ STANDARD] [ ] [ ] ( internal.access.Lister) ERROR - There was a problem with the database when getting a list:
com.pega.pegarules.pub.database.ConnectionException: Database-General Connection Exception 0 weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool PegaRULES to allocate to applications, please increase the size of the pool and retry..
DatabaseException caused by prior exception: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool PegaRULES to allocate to applications, please increase the size of the pool and retry..
| SQL Code: 0 | SQL State: null
DatabaseException caused by prior exception: java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:PegaRULES, props = {EmulateTwoPhaseCommit=false, connectionPoolID=PegaRULES, jdbcTxDataSource=true, LoggingLastResource=false, dataSourceName=PegaRULES}
| SQL Code: 0 | SQL State: null
at com.pega.pegarules.data.internal.access.ExceptionInformation.createAppropriateExceptionDueToDBFailure(ExceptionInformation.java:373) ~[prprivate.jar:?] at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:358) ~[prprivate.jar:?] at com.pega.pegarules.data.internal.store.ConnectionBrokerAdapter.getDataStoreConnection(ConnectionBrokerAdapter.java:178) ~[prprivate.jar:?] at com.pega.pegarules.data.internal.store.ConnectionBrokerRouter.getDataStoreConnection(ConnectionBrokerRouter.java:80) ~[prprivate.jar:?]Make the following change to the operating environment:Steps to Reproduce
Upgrade to Pega 7.4 and run a data flow.Root Cause
A defect or configuration issue in the operating environment.Resolution
Increase the JDBC connection pool size from 15 to max value of 30.
Tags:
Published August 30, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.