IBM Support

PM21978: JMS MESSAGES INTENDED FOR WEBSPHERE SERVICE INTEGRATION BUS V7.0.X DESTINATION ARE SENT TO _SYSTEM.EXCEPTION.DESTINATION

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

  • Messages sent to Websphere Service Integration Bus v7.0.x
    destination are routed to _SYSTEM.Exception.Destination.
    .
    FFDCs show the following error:
    Exception:com.ibm.ws.objectManager.TooManyTransactions
    Exception
    SourceId:com.ibm.ws.sib.msgstore.persistence.objectManager.
    BatchingContextImpl.<init>
    ProbeId:1:132:1.17
    Reporter:com.ibm.ws.sib.msgstore.persistence.objectManager.
    BatchingContextImpl@7e207e2
    com.ibm.ws.objectManager.TooManyTransactionsException:
    CWSOM1034E: An application attempted to start more that the
    defined maximum=1,000(long) number of transactions.
     at com.ibm.ws.objectManager.ObjectManagerState.get
       Transaction(ObjectManagerState.java:2047)
     at com.ibm.ws.objectManager.ObjectManager.getTransaction
       (ObjectManager.java:554)
     at com.ibm.ws.sib.msgstore.persistence.objectManager.
       BatchingContextImpl.<init>(BatchingContextImpl.java:127)
     at com.ibm.ws.sib.msgstore.persistence.objectManager.
       PersistentMessageStoreImpl.prepare(PersistentMessageStore
       Impl.java:1407)
     at com.ibm.ws.sib.msgstore.transactions.XidParticipant.
       prepare(XidParticipant.java:371)
     at com.ibm.ws.sib.msgstore.transactions.XidManager.prepare
       (XidManager.java:297)
     at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXA
       Resource.prepare(MSDelegatingXAResource.java:410)
     at com.ibm.tx.jta.JTAXAResourceImpl.prepare(JTAXAResource
       Impl.java:225)
     at com.ibm.tx.jta.RegisteredResources.prepareResource
       (RegisteredResources.java:1157)
     at com.ibm.tx.jta.RegisteredResources.distributePrepare
       (RegisteredResources.java:1413)
     at com.ibm.tx.jta.TransactionImpl.prepareResources
       (TransactionImpl.java:1438)
     at com.ibm.tx.jta.TransactionImpl.internalPrepare
       (TransactionImpl.java:1387)
     at com.ibm.tx.jta.JCATranWrapperImpl.prepare(JCATran
       WrapperImpl.java:177)
     at com.ibm.tx.jta.TxXATerminator.prepare(TxXATerminator.
       java:213)
     at com.ibm.ws.sib.transactions.impl.XAResourceWithSub
       ordinatesImpl.prepare(XAResourceWithSubordinatesImpl.
       java:397)
     at com.ibm.ws.sib.comms.server.clientsupport.StaticCATXA
       Transaction.rcvXAPrepare(StaticCATXATransaction.java:542)
    
    Following error message is seen on the SYSTEM.Exception.
    Destination Queue:
    
    CWSIK0035E: A message cannot be delivered to destination
    XYZ on messaging engine XXX because it has rolled back more
    times than its redelivery threshold.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server Version    *
    *                  7.0, with WebSphere MQ Server bus members,  *
    *                  using a filestore                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: CWSOM1034E when sending more than       *
    *                      1000 messages in a single               *
    *                      transaction, when there are WebSphere   *
    *                      MQ Server bus members                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The send of multiple messages within a single transaction
    should result in a single transaction branch within the
    messaging engine.
    
    However, the messaging engine discards information about the
    transaction branch too early in its processing, and as a
    result causes each send of the message to be contained within
    its own separate transaction branch. The creation of these
    separate transaction branches causes significant inefficiency,
    and prevents more than 1000 messages from being sent within a
    single transaction (when using filestore).
    

Problem conclusion

  • The fix for this APAR corrects the messaging engine code, so
    that all of the sends are correctly contained within a single
    transaction branch.
    
    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

    PM21978

  • 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-09-07

  • Closed date

    2010-10-29

  • Last modified date

    2010-10-29

  • 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 #: PM21978

Modified date: 29 October 2010