Support Article
DatabaseException trying to open conclusion property PXRDBERROR
SA-15847
Summary
A database connection error repeats in the PegaRULES logfile. Primary functions of the application are not working normally.
Error Messages
2015-09-10 18:19:16,678 [j2ee14_ws,maxpri=10]] [ STANDARD] [ ] ( internal.access.DatabaseImpl) ERROR - There was a problem with the database when getting a list:
com.pega.pegarules.pub.database.ConnectionException: Database-General Problem encountered when getting connection for database pegarules -4499 08001 [jcc][t4][2043][11550][3.58.81] Exception java.net.ConnectException: Error opening socket to server /127.0.0.1 on port 60,144 with message: A remote host did not respond within the timeout period.. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
From: (B6DA386576C3A2CE319016597A5EC9216)
Caused by SQL Problems.
Problem #1, SQLState 08001, Error code -4499: com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][2043][11550][3.58.81] Exception java.net.ConnectException: Error opening socket to server /127.0.0.1 on port 60,144 with message: A remote host did not respond within the timeout period.. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
Problem #2, SQLState 08001, Error code -4499: java.sql.SQLException: [jcc][t4][2043][11550][3.58.81] Exception java.net.ConnectException: Error opening socket to server /127.0.0.1 on port 60,144 with message: A remote host did not respond within the timeout period.. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:163)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1362)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:977)
at com.pega.pegarules.data.internal.access.ThreadConnectionStoreImpl.getConnection(ThreadConnectionStoreImpl.java:389)
....
at java.security.AccessController.doPrivileged(AccessController.java:276)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:796)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at java.lang.Thread.run(Thread.java:784)
Caused by:
com.ibm.websphere.ce.cm.StaleConnectionException: [jcc][t4][2043][11550][3.58.81] Exception java.net.ConnectException: Error opening socket to server /127.0.0.1 on port 60,144 with message: A remote host did not respond within the timeout period.. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
at sun.reflect.GeneratedConstructorAccessor2792.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java:610)
at com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java:669)
at com.ibm.ws.rsadapter.AdapterUtil.mapException(AdapterUtil.java:2271)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:2317)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getConnection(WSManagedConnectionFactoryImpl.java:1848)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1612)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1161)
at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:2107)
at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1785)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3272)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2610)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1500)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:1012)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:669)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:636)
at com.pega.pegarules.data.internal.access.DataSourceManager.getConnection(DataSourceManager.java:321)
at com.pega.pegarules.data.internal.access.DatabaseConnectionImpl.activate(DatabaseConnectionImpl.java:1350)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1312)
... 54 more
Steps to Reproduce
Unknown.
Root Cause
Intermittent connection issue with the database/ intermittent networking error.
Resolution
Work with your database and network teams to troubleshoot.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.