IBM Support

PI78935: TRANSACTIONS BECOME CORRUPTED AFTER CWSIC8007E, CWSIC2029E AND CWSIK0016E ERROR-MESSAGES IN THE JFAPCHANNEL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following kind of exception may lead to a unstable server
    state:
    
    [1/26/17 17:08:07:788 GMT+08:00] 00000257 XATransaction E
    J2CA0027E:
    An exception occurred while invoking prepare on an XA Resource
    Adapter
    from DataSource jms/fscs/factory/QCF, within transaction ID
    {XidImpl:
    formatId(57415344), gtrid_length(36), bqual_length(54),
    data
    (00000159da0833e0000000125c4a16688293495b4a29293a495c646ea73da6d
    c9c4771b
    900000159da0833e0000000125c4a16688293495b4a29293a495c646ea73da6d
    c9c4771b
    9000000010000000000000000000000000002)} : javax.transaction.xa.
    XAException: CWSIC8007E: An exception was caught from the remote
    server
    with Probe Id 3-013-0010. Exception: CWSIC2029E: This
    transaction
    cannot commit as an operation that was performed within the
    transaction
    boundary failed. The first operation that failed generated the
    following exception: com.ibm.ws.sib.processor.exceptions.
    SIMPIncorrectCallException: CWSIK0016E: The transaction used for
    send
    on the destination: Destination (931769395) CDA_AUDIT_QUEUE :
    14C8DC0FC558BEC401842E45 has already been completed...
                    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    parseSingleException(CommsByteBuffer.java:1753)
                    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    getException(CommsByteBuffer.java:1263)
                    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    checkXACommandCompletionStatus(CommsByteBuffer.java:1218)
                    at com.ibm.ws.sib.comms.client.
    OptimizedSIXAResourceProxy.prepare(OptimizedSIXAResourceProxy.ja
    va:749)
                    at
    com.ibm.ws.sib.comms.client.SuspendableXAResource.
    prepare(SuspendableXAResource.java:386)
                    at com.ibm.ws.sib.api.jmsra.impl.
    JmsJcaRecoverableSiXaResource.prepare(JmsJcaRecoverableSiXaResou
    rce.
    java:260)
    

Local fix

  • Whenever the exceptions occur the server needs to be restarted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  Transaction-based SIB Java Messaging        *
    *                  Service (JMS) communication                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Repeated CWSIC2029E / CWSIK0016E        *
    *                      errors within                           *
    *                      OptimizedSIXAResourceProxy.prepare()    *
    *                      calls on corrupted JMS connection.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a situation where a CWSIK0016E error occurs on a JMS
    connection, due to a misaligned understanding of the state
    of a JMS transaction id between client and server, this
    exception may be cached at the server side and sent back to
    the client for any subsequent operation attempting to use this
    JMS transaction id.
    If this condition is encountered, the client should close the
    existing JMS connection and re-establish it, to ensure the
    client and server's understanding of the connection's state is
    consistent.
    However, the exception sent back from the server for
    XAPrepare operations was incorrctly wrapped inside an
    XAException, which the client interpreted as being an exception
    from which recovery could be made without closing &
    re-establishing the connection.
    The fix stops the underlying exception from being wrapped in
    an XAException, thus causing the client to correctly close &
    re-establish the connection when it is encountered.
    When encountered, the following exception is seen repeatedly
    in the (client) system's trace:
    ----
    SIMPIncorrectCallException: CWSIK0016E: The transaction used
    for
    send
    on the destination: Destination (931769395) CDA_AUDIT_QUEUE :
    14C8DC0FC558BEC401842E45 has already been completed...
    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    parseSingleException(CommsByteBuffer.java:1753)
    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    getException(CommsByteBuffer.java:1263)
    at com.ibm.ws.sib.comms.common.CommsByteBuffer.
    checkXACommandCompletionStatus(CommsByteBuffer.java:1218)
    at com.ibm.ws.sib.comms.client.
    OptimizedSIXAResourceProxy.prepare(OptimizedSIXAResourceProxy.ja
    va:749)
    ----
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI78935

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-29

  • Closed date

    2017-11-27

  • Last modified date

    2017-11-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 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":"8.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021