A trace update was made to the J2C component which used
the wrong method call. This change was included in Application Server
versions 5.0.2.15, 5.1.1.8, and 6.0.2.5:
This exception will only be logged to the SystemOut.log and trace.log
if the following three conditions are met:
(1) Application Server versions 5.0.2.15, 5.1.1.8, and 6.0.2.5:
(2) WAS.j2c tracing is enabled.
(3) Aged and/or unused timeout is non-zero.
The exception occurs during the release of a destroyed connection when
the state of the connection is checked.
The following stack trace shows the failing code:
J2CA0079E: Method getManagedConnection has detected an internal
illegal state and is throwing an IllegalStateException. The exception is:
java.lang.IllegalStateException: setManagedConnection: illegal state
exception. State = STATE_INACTIVE
at com.ibm.ejs.j2c.MCWrapper.getManagedConnection(MCWrapper.java:707)
at com.ibm.ejs.j2c.poolmanager.PoolManager.release(PoolManager.java:1576)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:1945)
The line at
com.ibm.ejs.j2c.MCWrapper.getManagedConnection(MCWrapper.java:707)
should read at
com.ibm.ejs.j2c.MCWrapper.getManagedConnectionWithoutStateCheck
|