IBM Support

PM46561: WS-RELIABLE MESSAGING DOES NOT HANDLE 2PC TRANSACTIONS

Fixes are available

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
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
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 using WS-Reliable Messaging to send a message in a two
    phase transaction, the following exception occurs:
    
    Exception:com.ibm.ws.sib.msgstore.RollbackException
    
    SourceId:com.ibm.ws.sib.msgstore.transactions.XidManager.prepare
    
    ProbeId:1:303:1.60
    
    com.ibm.ws.sib.msgstore.RollbackException: CWSIS1002E: An
    unexpected
    exception was caught during transaction completion. Exception:
    java.lang.IllegalStateException: CWSIS1520E: The transaction
    is not in a legitimate state to perform the operation. It is in
    state: TransactionStatePreparing
    at
    com.ibm.ws.sib.msgstore.transactions.XidParticipant.prepare(XidP
    articipant.java:479) at
    com.ibm.ws.sib.msgstore.transactions.XidManager.prepare(XidMan
    ager.java:297) at
    com.ibm.ws.sib.msgstore.transactions.MSDelegatingXAResource.prep
    are(MSDelegatingXAResource.java:410) at
    com.ibm.ws.sib.comms.server.clientsupport.StaticCATXATransaction
    .rcvXAPrepare(StaticCATXATransaction.java:542) at
    com.ibm.ws.sib.comms.server.clientsupport.ServerTransportReceive
    Listener.dataReceived(ServerTransportReceiveListener.java:355)
    at
    com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ConversationRecei
    veListenerDataReceivedInvocation.invoke(ConversationReceiveListe
    nerDataReceivedInvocation.java:195) at
    com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ReceiveListenerDisp
    atchQueue.run(ReceiveListenerDispatchQueue.java:526) at
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:
    Caused by: java.lang.IllegalStateException: CWSIS1520E: The
    transaction is not in a legitimate state to perform the
    operation. It is in state: TransactionStatePreparing at
    com.ibm.ws.sib.msgstore.task.UpdateTask.persist(UpdateTask.java:
    233) at
    com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStor
    eImpl.prepare(PersistentMessageStoreImpl.java:593) at
    com.ibm.ws.sib.msgstore.transactions.XidParticipant.prepare(XidP
    articipant.java:371)
    ... 7 more
    
    As a result the two phase transaction rolls back.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WS-Reliable Messaging                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Two phase transactions involving        *
    *                      WS-Reliable Messaging roll back at      *
    *                      prepare time.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is caused by an incorrect state transition in the
    underlying Service Integration Bus resource manager
    transaction.  Due to a programming error, that transaction had
    started preparing as if it were in a one phase transaction
    before the two phase transaction prepare call was received
    from the transaction manager.  This causes the
    IllegalStateException and so the two phase transaction rolls
    back.
    This does not result in a non-atomic outcome for the
    transaction because all resources involved in the two phase
    transaction rollback, including the WS-Reliable Messaging
    resource.
    

Problem conclusion

  • This APAR corrects the programming error to ensure correct
    intereaction between WS-Reliable Messaging and the underlying
    Service Integration Bus transaction, and the two phase
    transaction proceeds as expected.
    
    Before uninstalling this APAR or a fix pack that contains this
    APAR it is recommended that any sequences are quiesced.  If
    not there is a chance that until the APAR is reapplied any
    sequences that existed prior to the uninstall cannot be
    deleted.  WS-Reliable Messaging functionality is unaffected by
    this.  Simply the sequence cannot be deleted until the APAR is
    reapplied.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.23 and 8.0.0.4.  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

    PM46561

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-29

  • Closed date

    2012-01-24

  • Last modified date

    2012-01-24

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM46561

Modified date: 24 January 2012