IBM Support

PM40146: ILLEGAL STATE AFTER RECONNECT WITH JMS RESOURCE ADAPTER

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The problem occurs when a MDB (message driven bean) in an
    application connects with Java Message Service (JMS) when using
    a resource adapter configuration. If the JMS connection is
    broken and later recovered, a restart of the JVM will lead to
    an "illegal state exception".
    
    Getting the error below:
    
    [3/29/11 11:21:47:828 CEST] 00000011 MCWrapper     E
    J2CA0079E: Method
    cleanup has detected an internal illegal state and is throwing
    an IllegalStateException. The exception is:
    java.lang.IllegalStateException: cleanup: illegal state
    exception. State= STATE_INACTIVE MCW = 3fe43fe4
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1426)
    at
    com.ibm.ejs.j2c.FreePool.cleanupAndDestroyMCWrapper(FreePool.jav
    a:712)
    at
    com.ibm.ejs.j2c.FreePool.removeParkedConnection(FreePool.java:76
    2)
    at
    com.ibm.ejs.j2c.PoolManager.serverShutDown(PoolManager.java:1482
    )
    at
    com.ibm.ejs.j2c.ConnectionServerShutDownFactoryImpl.shutdown(Con
    nectionS
    erverShutDownFactoryImpl.java:94)
    at
    com.ibm.ejs.j2c.RALifeCycleManagerImpl.shutdown(RALifeCycleManag
    erImpl.j
    ava:1396)
    at
    com.ibm.ejs.j2c.RALifeCycleManagerImpl.stop(RALifeCycleManagerIm
    pl.java:
    462)
    at
    com.ibm.ws.runtime.component.ContainerImpl.stopComponents(Contai
    nerImpl.
    java:1036)
    at
    com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.ja
    va:685)
    

Local fix

  • Candidate to be fixed in next release.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a server shuts down, a J2CA0079E   *
    *                      message is seen in traces.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the server is shuting down, as part of cleanup of
    connections in the pool, traces might have the following
    exception:
    [3/29/11 11:21:47:828 CEST] 00000011 MCWrapper     E
    J2CA0079E: Method cleanup has detected an internal illegal
    state and is throwing an IllegalStateException. The exception
    is:
    java.lang.IllegalStateException: cleanup: illegal state
    exception. State= STATE_INACTIVE MCW = 3fe43fe4
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1426)
    at
    com.ibm.ejs.j2c.FreePool.cleanupAndDestroyMCWrapper(FreePool.jav
    a:712)
    at
    com.ibm.ejs.j2c.FreePool.removeParkedConnection(FreePool.java:76
    2)
    at
    com.ibm.ejs.j2c.PoolManager.serverShutDown(PoolManager.java:1482
    )
    The pool tries to close the connections as part of shutdown
    while the server is stopping. We might encounter the illegal
    state exception due to various reasons. As this is expected
    during server shutdown, we are going to log this in trace.
    

Problem conclusion

  • We now log the message as part of tracing rather than throwing
    the exception.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.43 and 7.0.0.21 and 8.0.0.2.  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

    PM40146

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-26

  • Closed date

    2011-08-26

  • Last modified date

    2011-08-26

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM40146

Modified date: 26 August 2011