SQL exceptions in IDM logs

[Lalitha Lakshmi]

Hello!

 

We are having issues with our IDM setup, every now and then with the below exceptions in the logs:

 

[6/27/18 14:38:31:643 EDT] 00000384 ConnectionEve W   J2CA0206W: A connection error occurred.  To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option.

[6/27/18 14:38:31:645 EDT] 00000384 ConnectionEve A   J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource iam/im/jdbc/jdbc/idm. The exception is: java.sql.SQLRecoverableException: IO Error: Connection timed out:java.net.SocketException: Connection timed out

[6/27/18 14:38:31:892 EDT] 00000384 WSRdbManagedC W   DSRA0180W: Exception detected during ManagedConnection.destroy().  The exception is:  com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Closed Connection. with SQL State : 08003 SQL Code : 17008

        at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:3921)

        at oracle.jdbc.OracleConnectionWrapper.rollback(OracleConnectionWrapper.java:145)

        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions(WSRdbManagedConnectionImpl.java:4484)

        at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.destroy(WSRdbManagedConnectionImpl.java:3656)

        at com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1855)

        at com.ibm.ejs.j2c.FreePool.cleanupAndDestroyMCWrapper(FreePool.java:745)

 

Idm is hosted on WAS servers and uses Oracle 11g as its database. Versions are as follows:

IDM- 12.6.1

RHEL 5.11

Oracle Enterprise Edition Release 11.2.0.3.0

JDBC driver version  : 11.2.0.3.0

 

These errors go away once we restart the JVMs. Has anyone else faced these issues?

 

Thanks!

Lalitha

[KennyV]

IM 12.6.1 is an older product version which has already reached end of service in December 2017. I would suggest reviewing the release notes for versions/patches released since then to see if there is any mention of a similar problem that may have already been fixed. I would also suggest upgrading to the latest product release (which at this time is IM 14.2) in order to benefit from the latest fixes and new features. If you have an extended support agreement then another option would be to open a support case.

 

Sid_Mautte, including you in case you had any insight.