IBM Support

PM21176: SIB ERRORS CWSIC8002E, CWSIC8007E, CWSIC1007E, CWSIC1008E, CWSIC2059E AND CWSIK0016E ISSUED WHILE HANDLING XA TRANSACTIONS

Fixes are available

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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

  • When JMS applications connect to a Service Integration Bus
    messaging engine, they may be issued a new connection or reuse
    one from a connection pool.  The SIB code can give a connection
    to the wrong messaging engine to the transaction manager, which
    causes unexpected errors during transaction completion:
    .
      CWSIC8002E: An internal error occurred.  An unknown or
        unexpected exception was thrown by the core API
      CWSIC8007E: An exception was caught from the remote server
        with Probe Id 3-004-0013.
      CWSIC1007E: rollback(XID) not possible as the supplied XID is
        not recognized by the messaging engine
      CWSIC1008E: rollback(XID) not possible as the supplied XID has
        not yet been called to end it's association with the
        messaging engine
      CWSIC2059E: An internal error occurred. An attempt was made to
        get an object from the map with id 9, but there is no item
        in the map with this key.
      CWSIK0016E: The transaction used for send on the destination
        ■... has already been completed.
    

Local fix

  • A previous APAR PM07867 fixed this issue for applications which
    do not specify user credentials in their connections.  Going to
    fix pack 7.0.0.11 will solve this problem for such applications.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server Version 7  *
    ****************************************************************
    * PROBLEM DESCRIPTION: XAException or SIErrorException when    *
    *                      attempting to complete an               *
    *                      XA transaction on an authenticated      *
    *                      JMS connection.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The default messaging provider code incorrectly allows
    the messaging engine connection passed to the transaction
    manager (in a JmsJcaSessionImpl object) to be connected to a
    different messaging engine to the connection used when
    performing the sends/receives (in a JmsSessionImpl object).
    
    The problem occurs when an authenticated JMS connection obtains
    its connection to the messaging engine from the connection pool,
    rather than creating a new connection. This connection is used
    when performing sends/receives etc. for any session created
    from that connection, and also should provide a model for all
    connections created for transaction coordination of individual
    sessions. However, the code incorrectly fails to store a
    reference to the connection in the correct place for it to be
    used as the model for creating messaging engine connections
    for transaction coordination. This means the
    connection passed to the transaction manager to control
    the transaction of a session might be connected to a different
    messaging engine, which then rejects the attempt to
    prepare/commit/rollback the transaction.
    
    The problem is most likely to occur when multiple messaging
    engines for the same bus are running in a single JVM, and the
    application is running locally within that same JVM.
    

Problem conclusion

  • The fix for this APAR ensures that when an authenticated JMS
    connection obtains its messaging engine connection from an
    existing connection in the pool, it stores it in the correct
    place to be used as a model for creation of connections for
    transaction coordination of individual sessions using that
    connection.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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

    PM21176

  • 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

    2010-08-24

  • Closed date

    2010-09-27

  • Last modified date

    2010-09-27

  • 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



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM21176

Modified date: 27 September 2010