IV47459: A WEBSPHERE MQ MESSAGING PROVIDER ACTIVATION SPECIFICATION IN WSAS ISSUES ERROR JMSCC0034 ABOUT BEING IN AN INCONSISTENT STATE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Each WebSphere MQ activation specification has a pool of
    ServerSession threads which it uses to deliver messages to
    Message Driven Beans (MDBs).  It is possible for one of these
    ServerSessions to be left in an inconsistent state, such that
    each time it is used, an ffdc is issued with these details:
    .
    FFDC Exception:
    com.ibm.msg.client.jms.DetailedIllegalStateException
    SourceId:endDeliverInternal()
    ProbeId:XJ009003
    Reporter:java.util.HashMap@xxxxxxxx
    com.ibm.msg.client.jms.DetailedIllegalStateException:
    JMSCC0034: The asynchronous delivery mechanism is in an
    inconsistent state in method: 'deliver'. An unexpected
    sequence of events has been detected during delivery of
    messages to a message-driven bean (MDB). This may be caused
    by client programming application errors.
    .
    .
    Although message delivery continues, the invalid ServerSession
    object slows message throughput.  This problem may occur after
    an exception like javax.resource.spi.work.WorkRejectedException
    (e.g. APAR IV47458) or for other reasons.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7 Resource Adapter.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    
    who are using an Activation Specification to drive an MDB by
    consuming messages from a WebSphere MQ queue.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    ServerSessions are objects used by the WebSphere MQ Resource
    Adapter (WMQ-RA) when using an activation specification to drive
    an MDB from a WebSphere MQ queue.
    
    When in use, ServerSessions contain data to uniquely identify
    messages on the WebSphere MQ queue, called a MessageReference.
    
    A ServerSession should only contain MessageReference data when
    it is currently in use. Accordingly, it is not valid for a
    ServerSession to contain MessageReference data when the
    ServerSession
    is not in use. When a ServerSession is picked from the
    pool to be loaded up with MessageReference data, a check is
    performed on the integrity of ServerSession.  If it is found to
    contain MessageReference data, an exception is thrown (with an
    associated FDC), containing the message:
    
    ----------------------------------------------------------------
    com.ibm.msg.client.jms.DetailedIllegalStateException:
    JMSCC0034: The asynchronous delivery mechanism is in an inconsis
    tent state in method: 'deliver'. An unexpected sequence of event
    s has been detected during delivery of messages to a message-
    driv
    en bean (MDB). This may be caused by client programming applicat
    ion errors.
    ----------------------------------------------------------------
    
    After this exception has been thrown, the MDB processing for the
    specific message which was to be processed is aborted, and the
    message will not be picked up again by the activation
    specification until after the a time period specified by the
    queue manager property "MARKINT", which defaults to 5 seconds.
    
    
    If the application server fails to start the unit of work
    associated with MDB processing within the configured timeout
    value (see APAR IV47458 for details on reasons for this), the
    ServerSession was put back into the ServerSession pool without
    clearing the MessageReference data, leading to this JMSCC0034
    message being displayed.
    

Problem conclusion

  • The code was modified to ensure that if the unit of work
    associated with starting an MDB fails with the exception:
    
    javax.resource.spi.work.WorkRejectedException
    
    the ServerSession is not returned to the pool with the
    contaminating MessageReference data.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.12
    v7.1       7.1.0.5
    v7.5       7.5.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV47459

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-23

  • Closed date

    2013-09-12

  • Last modified date

    2013-09-12

  • 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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere MQ
APAR / Maintenance

Software version:

7.0.1

Reference #:

IV47459

Modified date:

2013-09-12

Translate my page

Machine Translation

Content navigation