IBM Support

PM12356: UNCAUGHT NULLPOINTEREXCEPTION PREVENTS FURTHER MESSAGE PROCESSING BY MDBS RUNNING ON WEBSPHERE APPLICATION SERVER

Fixes are available

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
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

  • Messages pile up on Default.Topic.Space and the following
    error is logged in the WebSphere Application Server
    SystemOut.log:
    
    J2CA0027E: An exception occurred while invoking prepare on an
    XA Resource Adapter from dataSource XXX, within transaction ID
    {XidImpl: formatId(57415344), gtrid_length(36),bqual_length(54),
    data(nnn)}: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.SIMPLimitExceededException:
    CWSIP0251E:The destination Default.Topic.Space on messaging
    engine XXX is not available because the high limit 50,000 for
    the number of messages for this destination has already been
    reached..
    
    Prior to the above error, NullPointerException is logged in
    the SystemErr.log:
    Exception in thread "Asynchronous Consumer : XXX" java.lang.
    NullPointerException
    at com.ibm.ws.sib.comms.client.proxyqueue.queue.ReadAheadQueue.
       deliverBatch(ReadAheadQueue.java:750)
    at com.ibm.ws.sib.comms.client.proxyqueue.impl.AsynchConsumer
       ProxyQueueImpl.deliverMessages(AsynchConsumerProxyQueueImpl.
       java:748)
    at com.ibm.ws.sib.comms.client.proxyqueue.asynch.AsynchConsumer
       ThreadPool$ScheduleQueue.run(AsynchConsumerThreadPool.
       java:197)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
    

Local fix

  • Restart all the JVMs in the environment
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  Version 6.1 and Version 7                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: A consumer using read ahead stops       *
    *                      receiving messages, after a             *
    *                      NullPointerException from               *
    *                      ReadAheadQueue.deliverBatch()           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is most likely to affect publish/subscribe
    applications, where read ahead is enabled by default for
    consumers.
    
    An uncaught NullPointerException within the read ahead
    logic causes a consumer thread owned by the JMS provider to be
    abruptly terminated. This prevents any further messages from
    being delivered to the consumer.
    
    For non-durable publish/subscribe the broken consumer
    still remains subscribed, so the topic space expects it to
    continue to process messages.
    As it does not, the messages pile up on the topic and
    eventually the high limit for the destination is reached, with
    an SIMPLimitExceededException being thrown.
    No further messages can be sent to the topic.
    
    The reason that the NullPointerException occurred was access
    to a read ahead data structure without correct synchronization,
    resulting in dirty reads / writes causing invalid data
    to be returned by the underlying Java collection.
    

Problem conclusion

  • The fix for this APAR adds additional locking before the read
    ahead data structure is accessed, in order to prevent the dirty
    reads / writes.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.33 and 7.0.0.13.  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

    PM12356

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-16

  • Closed date

    2010-06-01

  • Last modified date

    2010-06-01

  • 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

    620600101

Applicable component levels

  • R200 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.1

Reference #: PM12356

Modified date: 01 June 2010