IBM Support

PI71193: Illegal State Exception when transaction timeout occurs and abort is used

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a transaction timeout occurs and a JDBC 4.1 compliant
    driver is used the connection is aborted.  When using
    SQLServer the following exception occurs:
    
    java.lang.IllegalStateException: getManagedConnection:
    illegal state exception. State = STATE_INACTIVE MCW =
    12630118
    	at
    com.ibm.ejs.j2c.MCWrapper.getManagedConnection(MCWrapper.jav
    a:745)
    	at
    com.ibm.ejs.j2c.PoolManager.fatalErrorNotification(PoolManag
    er.java:1264)
    	at
    com.ibm.ejs.j2c.MCWrapper.connectionErrorOccurred(MCWrapper.
    java:2495)
    	at
    com.ibm.ejs.j2c.ConnectionEventListener.connectionErrorOccur
    red(ConnectionEventListener.java:291)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processC
    onnectionErrorOccurredEvent(WSRdbManagedConnectionImpl.java:
    1835)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processC
    onnectionErrorOccurredEvent(WSRdbManagedConnectionImpl.java:
    1736)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.connecti
    onClosed(WSRdbManagedConnectionImpl.java:588)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerPooledConnection.notif
    yEvent(SQLServerPooledConnection.java:140)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnection.notifyPoole
    dConnection(SQLServerConnection.java:3710)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnection.poolCloseEv
    entNotify(SQLServerConnection.java:2133)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolProxy$1.
    run(SQLServerConnectionPoolProxy.java:161)
    	at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
    Executor.java:1142)
    	at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
    lExecutor.java:617)
    	at java.lang.Thread.run(Thread.java:745)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using a JDBC 4.1 Complient Driver    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Illegal State Exception when            *
    *                      transaction timeout occurs and abort is *
    *                      used                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a transaction timeout occurs and a JDBC 4.1 compliant
    driver is used the connection is aborted.  When using certain
    drivers (such as SQLServer) the following exception occurs:
    
    java.lang.IllegalStateException: getManagedConnection: illegal
    state exception. State = STATE_INACTIVE MCW = 12630118
    	at
    com.ibm.ejs.j2c.MCWrapper.getManagedConnection(MCWrapper.java:74
    5)
    	at
    com.ibm.ejs.j2c.PoolManager.fatalErrorNotification(PoolManager.j
    ava:1264)
    	at
    com.ibm.ejs.j2c.MCWrapper.connectionErrorOccurred(MCWrapper.java
    :2495)
    	at
    com.ibm.ejs.j2c.ConnectionEventListener.connectionErrorOccurred(
    ConnectionEventListener.java:291)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConne
    ctionErrorOccurredEvent(WSRdbManagedConnectionImpl.java:1835)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processConne
    ctionErrorOccurredEvent(WSRdbManagedConnectionImpl.java:1736)
    	at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.connectionCl
    osed(WSRdbManagedConnectionImpl.java:588)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerPooledConnection.notifyEve
    nt(SQLServerPooledConnection.java:140)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnection.notifyPooledCon
    nection(SQLServerConnection.java:3710)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnection.poolCloseEventN
    otify(SQLServerConnection.java:2133)
    	at
    com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolProxy$1.run(
    SQLServerConnectionPoolProxy.java:161)
    	at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1142)
    	at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:617)
    	at java.lang.Thread.run(Thread.java:745)
    

Problem conclusion

  • The code was modified to ensure that the connection is properly
    aborted when a transaction timeout occurs.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 9.0.0.2 for WebSphere Application Server and fix pack
    16.0.0.4 for WebSphere Application Server Liberty.  Please refer
    to the Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71193

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-24

  • Closed date

    2016-11-01

  • Last modified date

    2016-11-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021