IBM Support

PM31431: SERVICE INTEGRATION BUS TRANSACTION REMAINS INDOUBT AFTER MESSAGING ENGINE DATABASE OUTAGE

Fixes are available

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 the messaging engine database suffers an outage, it is
    possible that Service Integration Bus (SIB) transactions remain
    indoubt indefinitely.  Any messages associated with that
    transaction remain locked and the transaction must be manually
    resolved.
    
    When this problem occurs messages in the SystemOut log will
    indicate that SIB responded with XAER_RMFAIL to xa_prepare
    followed by XAER_PROTO to xa_rollback or nothing further.
    
    WTRN0046E: An attempt by the transaction manager to call
    prepare on a transactional resource has resulted in an error.
    The error code was XAER_RMFAIL. The exception stack trace
    follows: javax.transaction.xa.XAException: CWSIC8007E: An
    exception was caught from the remote server with Probe Id
    3-013-0010. Exception: .
    at java.lang.Throwable.<init>(Throwable.java:67)
    at
    com.ibm.ws.sib.comms.common.CommsByteBuffer.parseSingleException
    (CommsByteBuffer.java:1694)
    at
    com.ibm.ws.sib.comms.common.CommsByteBuffer.getException(CommsBy
    teBuffer.java:1263)
    at
    com.ibm.ws.sib.comms.common.CommsByteBuffer.checkXACommandComple
    tionStatus(CommsByteBuffer.java:1218)
    at
    com.ibm.ws.sib.comms.client.OptimizedSIXAResourceProxy.prepare(O
    ptimizedSIXAResourceProxy.java:746)
    ...
    
    An FFDC at the messaging engine server will also indicate the
    same problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Service Integration Bus transactions    *
    *                      remain indoubt indefinitely following   *
    *                      an outage of the messaging engine       *
    *                      database.                               *
    ****************************************************************
    * RECOMMENDATION:  The transactions must be resolved           *
    *                  manually.                                   *
    *                  NB: Care must be taken to ensure the        *
    *                  correct direction for the transaction is    *
    *                  chosen (i.e. commit or rollback) in order   *
    *                  to avoid data loss or duplication. Some     *
    *                  investigation may be required in some       *
    *                  cases to determine the correct direction.   *
    *                  If unsure, contact IBM support.             *
    *                  The following script can be used to         *
    *                  manually resolve the transaction:           *
    *                  http://publib.boulder.ibm.com/infocenter/wa *
    *                  s                                           *
    *                  info/v7r0/index.jsp?topic=/com.ibm.webspher *
    *                  e                                           *
    *                  .nd.multiplatform.doc/info/ae/ae/tjm0165_.h *
    *                  t                                           *
    *                  ml                                          *
    ****************************************************************
    A discrepancy between the in-memory state of the messaging
    engine and that persisted to its database caused the messaging
    engine to report that a transaction had not prepared
    successfully, when in fact it had.  The discrepancy arose from
    a failure at a particular point when the messaging engine was
    communicating with the database.
    

Problem conclusion

  • Better state maintenance ensures that when the particular
    failure occurs, the correct transaction outcome results.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.  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

    PM31431

  • 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

    2011-01-28

  • Closed date

    2011-02-22

  • Last modified date

    2012-06-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

    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 #: PM31431

Modified date: 26 June 2012