IBM Support

IT11393: ACTIVATION SPEC ENDPOINT PAUSES BEFORE THE SEQUENTIAL MESSAGE FAILURE LIMIT HAS BEEN REACHED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • An Activation Specification, defined against the WebSphere MQ
    messaging provider, running within WebSphere Application Server
    was configured to pause message delivery to the endpoint after a
    number of sequential message delivery failures. However the
    endpoint was being paused before the configured number of
    sequential message delivery failures had been reached.
    
    The test case exhibiting this problem configured the Activation
    Specification to pause the endpoint after ten sequential message
    delivery failures. The message-driven bean (MDB) application's
    input queue was configured with a backout threshold of five. A
    poison message was put on the MDB application's input queue and
    delivered to the onMessage(java.jms.Message) method. The
    application failed to process the message and it was rolled back
    to the input queue. This process repeated another four times
    before the message was moved to the backout requeue queue. At
    this point the sequential message delivery failure count was
    five. A non-poison message was then put on the MDB's input
    queue, which was successfully processed by the application.
    
    The expectation was that at this point the sequential message
    delivery failure count would be zero. A second poison message
    was then put on the MDB's input queue, which was delivered to
    the MDB and rolledback five times before being moved to the
    backout requeue queue.
    
    At this point, WebSphere Application Server paused the messaging
    endpoint and the following log message was reported in the
    WebSphere Application Server job log:
    
    SourceId: com.ibm.ws.sib.utils.ras.SibMessage
    ExtendedMessage: [:]
    CWWMQ0007W: The message endpoint
     has been paused by the system.
    Message delivery failed to the endpoint more than
    10 times.
    The last attempted delivery failed with the
    following error:
    javax.jms.TransactionRolledBackException:
    at com.ibm.mq.connector.inbound.AbstractWorkImpl.
       xaStateChanged (AbstractWorkImpl.java:411)
    at com.ibm.mq.connector.xa.XAObservable.update
      (XAObservable.java:120)
    at com.ibm.mq.connector.xa.XARWrapper.rollback
      (XARWrapper.java:490)
    at com.ibm.tx.jta.impl.JTAXAResourceImpl.rollback
      (JTAXAResourceImpl.java:381)
    at com.ibm.tx.jta.impl.RegisteredResources.
       deliverOutcomeRegisteredResources.java:1717)
    at com.ibm.tx.jta.impl.RegisteredResources.
       distributeOutcomeRegisteredResources.java:2003)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere Application Server for z/OS V8.5 WebSphere MQ
    messaging provider.
    
    who are making use of the "Stop endpoint if message delivery
    fails" function and are making a BINDINGS transport mode
    connection to a WebSphere MQ for z/OS queue manager.
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the "Stop endpoint if message delivery fails" function is
    enabled for a WebSphere MQ Activation Specification within
    WebSphere Application Server, the value of the corresponding
    property:
    
      "Number of sequential delivery failures before suspending
    endpoint"
    
    is used to control the point at which the endpoint is suspended,
    following a series of failures to process messages.
    
    If a message-driven bean (MDB) application fails to process a
    message, the sequential delivery failure counter for that
    endpoint is incremented. Should the MDB application successfully
    processes a message, and any transaction under which the message
    was processed committed, the counter should be reset to zero.
    
    When WebSphere Application Server for z/OS connects to a
    WebSphere MQ for z/OS queue manager using the BINDINGS transport
    mode, the sequential delivery failure counter was not reset to
    zero following a successfully processed message. This was due to
    the WebSphere MQ Resource Adapter failing to inform WebSphere
    Application Server, that controls the state of the sequential
    delivery failure counter, that a message had been processed
    successfully.
    
    This resulted in the message endpoint being suspended earlier
    than expected, i.e., before the configured value for the number
    of sequential delivery failures had been satisfied.
    

Problem conclusion

  • The WebSphere MQ Resource Adapter has been updated to inform the
    WebSphere Application Server with the correct information once a
    message has been processed successfully, such that the
    sequential delivery failure counter can be reset to zero
    accordingly.
    
    The result of this is that the WebSphere Application Server will
    now suspend the message endpoint once the "Number of sequential
    delivery failures before suspending endpoint" limit has been
    reached.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.8
    v7.5       7.5.0.6
    v8.0       8.0.0.5
    
    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

    IT11393

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-23

  • Closed date

    2015-10-30

  • Last modified date

    2015-10-30

  • 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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 October 2015