Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Intermittently dropping the DB connections to ODN

SA-13295

Summary



Intermittently dropping the Oracle DB connections on Websphere while going thru F5. Getting below exception if PEGARules DataSource is configured with F5 VIP on 1521(default oracle ports).
Exceptions trace:


Error Messages


[8/6/15 9:46:12:947 MST] 00000031 ConnectionEve W J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Co
nnection Factory or Data Source. This is the multithreaded access detection option. Alternatively check that the Database or MessageProvider is available.
[8/6/15 9:46:12:948 MST] 00000031 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jdbc/PegaRULES. Th
e exception is: java.sql.SQLRecoverableException: IO Error: Connection reset:java.net.SocketException: Connection reset
[8/6/15 9:46:12:953 MST] 00000031 MCWrapper E J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection [email protected]
4b1 from resource jdbc/PegaRULES. Caught exception: com.ibm.ws.exception.WsException: DSRA1130E: A fatal connection error occurred on another connection while this connection wa
s active. This connection cannot be reset to a usable state.
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:251)
at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.<init>(DataStoreAdapterException.java:200)
at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:444)
at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRdbManagedConnectionImpl.java:4051)
at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1553)
at com.ibm.ejs.j2c.FreePool.cleanupAndDestroyMCWrapper(FreePool.java:738)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2766)


Steps to Reproduce



1)Configured the PEGA Rules data source with F5 VIP in jdbc URL( jdbc:oracle:thin:@<F5 VIP>:1521/DB_NAME).
2)Restart the JVM and leave the environment for 5-6 hrs.
3)Check the logs for exception.


 

Root Cause



A defect or configuration issue in the operating environment.  The JDBC connection closed/timeout issue only happens when they connect to ODN X-5 that is the F5 load balanced Oracle 12c DB.
 

Resolution



Make the following change to the operating environment: Enable 'Validate connections' option under 'WebSphere Application Server data source properties'.

Published August 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us