IBM Support

PK93592: APPLICATION RUNNING INSIDE A THIRD PARTY APPLICATION SERVER FAILS TO RECONNECT IF A MESSAGING ENGINE IS RESTARTED

Fixes are available

7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 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 issue relates to an environment using the IBM Resource
    Adapter for JMS with WebSphere Application Server, supplied
    with WebSphere Application Server Version 7.0, within a third
    party application server.
    
    The problem was initially reported when a messaging engine was
    stopped and restarted and message-driven bean running in the
    third party application server failed to reconnect and consume
    messages. The failure to reconnect is caused by the following
    runtime exception:
    .
    java.lang.NoClassDefFoundError:
    com.ibm.wsspi.channel.framework.CFEndPoint
    at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
    executeRedirect(TrmSICoreConnectionFactoryImpl.java:851)
    at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
    remoteBootstrap(TrmSICoreConnectionFactoryImpl.java:605)
    at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
    createConnection(TrmSICoreConnectionFactoryImpl.java:301)
    at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
    createConnection(TrmSICoreConnectionFactoryImpl.java:216)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection
    .createConnection(SibRaMessagingEngineConnection.java:1079)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection
    .<init>(SibRaMessagingEngineConnection.java:657)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation
    .connectUsingTrmWithTargetData(
    SibRaCommonEndpointActivation.java:646)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    connectUsingTrm(SibRaCommonEndpointActivation.java:554)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    connect(SibRaCommonEndpointActivation.java:458)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    checkMEs(SibRaCommonEndpointActivation.java:338)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    timerLoop(SibRaCommonEndpointActivation.java:297)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    dropConnection(SibRaCommonEndpointActivation.java:1371)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
    messagingEngineQuiescing(
    SibRaCommonEndpointActivation.java:1253)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection
    $SibRaConnectionEventThread.executeCallback(
    SibRaMessagingEngineConnection.java:1408)
    at com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection
    $SibRaConnectionEventThread.run(
    SibRaMessagingEngineConnection.java:1368)
    at java.lang.Thread.run(Thread.java:797)
    .
    This exception occurs inside the callback that informs the
    resource adapter that the messaging engine is stopping, and in
    which it is attempting to reconnect to the messaging engine
    (before the failover is complete).
    The code throws this runtime exception while building an
    exception due to incorrectly using some classes that only
    exist when running inside IBM WebSphere Application Server.
    The throwing of this exception prevents a retry timer from
    being registered, so the endpoint does not automatically
    reconnect to the messaging engine when it does become
    available after the failover.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the IBM Resource Adapter for JMS   *
    *                  with WebSphere Application Server, or the   *
    *                  IBM Thin Client for Java Messaging Service  *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NoClassDefFoundError exception is     *
    *                      thrown when attempting to connect to    *
    *                      the bus in a failover scenario from a   *
    *                      stand-alone thin client                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following exception is thrown during an attempt to connect
    to the bus:
    java.lang.NoClassDefFoundError:
    com.ibm.wsspi.channel.framework.CFEndPoint
    at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
          executeRedirect(TrmSICoreConnectionFactoryImpl.java:851)
    
    This runtime exception is most likely to occur when a
    messaging engine is hosted in a cluster, and is stopped.
    The exception might be thrown to J2SE application code using
    the IBM Thin Client for Java Messaging Service.
    It is most likely to be thrown to the reconnection logic of the
    IBM Resource Adapter for JMS with WebSphere Application
    Server, leaving it in an inconsistent state where it does not
    reconnect to the bus after a failure.
    
    The exact scenario in which the error occurs is as follows:
    - The client loses its connection to the messaging engine
      because the messaging engine is stopped.
    - The client immediately attempts to reconnect, and contacts
      the first bootstrap server specified in the provider
      endpoints list of the connection factory.
    - The workload-management information in the bootstrap server
      indicates the messaging engine is still running on the
      server in the cluster where it has just been stopped, so
      redirects the client to that server.
    - The client performs the redirect, but the messaging engine
      is no longer available on the other server, because it is
      stopping.
    - A NoClassDefFoundError runtime exception occurs while
      creating a CWSIT0099E error message to throw. This runtime
      exception occurs because the code attempts to access a
      class that only exists in WebSphere Application Server
      client environments.
    

Problem conclusion

  • The fix for this APAR corrects the code that creates the
    CWSIT0099E exception, preventing the NoClassDefFoundError
    exception from being thrown.
    This allows the reconnection logic of the IBM Resource Adapter
    for JMS with WebSphere Application Server to operate correctly
    in a third party application server environment.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  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

    PK93592

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-11

  • Closed date

    2009-10-05

  • Last modified date

    2009-10-05

  • 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

    PLAT MSG COM

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021