IBM Support

PM11871: LARGE NUMBER OF WTRN0078E ERROR MESSAGES WRITTEN TO THE WEBSPHERE APPLICATION SERVER SYSTEMOUT.LOG

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
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
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • Websphere Application Server hosting a Message Driven Bean
    (MDB) application produces a large number of WTRN0078E error
    messages .
    
    WTRN0078E: An attempt by the transaction manager to call start
    on a transactional resource has resulted in an error. The
    error code was XAER_INVAL. The exception stack trace follows:
    at com.ibm.ws.sib.comms.client.SIXAResourceProxy.start(SIXA
    ResourceProxy.java(Compiled Code))
    at com.ibm.ws.sib.ra.inbound.impl.SibRaXaResource.start(SibRa
    XaResource.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(JTA
    ResourceBase.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.RegisteredResources.startRes
    (RegisteredResources.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.RegisteredResources.enlist
    Resource(RegisteredResources.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource
    (TransactionImpl.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.TranManagerImpl.enlist(Tran
    ManagerImpl.java(Compiled Code))
    at com.ibm.ws.Transaction.JTA.TranManagerSet.enlist(Tran
    ManagerSet.java(Inlined Compiled Code))
    
    The MDB cannot process any messages.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Websphere Application Server hosting    *
    *                      a Message Driven Bean application       *
    *                      produces a large number of WTRN0078E    *
    *                      error messages.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is caused by an earlier XA problem which may be
    recorded in an FFDC where an Message Driven Bean
    (MDB) application thread failed to xa_end a transaction
    because of an Exception. This leaves the XAResource used by
    the MDB thread in an inconsistent state at the end of the
    transaction (enlisted).  The MDB application thread reuses the
    XAResource and consequently is unable to start a new
    transaction using that XAResource because it is still enlisted
    with the old transaction.  Attempts to start the transaction
    fail with XAER_INVAL.
    
    This error is reported by the Transaction Service using the
    WTRN0078E, which is logged every time an MDB thread is
    dispatched with a message.
    
    In addition to the large number of WTRN0078E messages, it is
    possible that a transaction at the Messaging Engine (ME) is
    orphaned (enlisted and not ended) by the first failure to end a
    transaction.
    

Problem conclusion

  • This APAR resolves the problem by destroying the connection to
    the ME, causing the MDB to reconnect.  This creates a new
    XAResource and rolls back any transactions at the ME that are
    unresolved.
    
    This APAR also changes the XA error code returned when
    attempting to start a transaction with an enlisted XAResource
    from XAER_INVAl to XAER_PROTO which adheres more closely to
    the XA specification.  There is no functional consequence of
    this.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.43, 6.1.0.35 and 7.0.0.13.  Please refer to the
    Recommended Updatespage for delivery information:
    
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM11871

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620400101

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-09

  • Closed date

    2010-07-05

  • Last modified date

    2010-07-05

  • 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

    620400101

Applicable component levels

  • R100 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021