IBM Support

IT27995: The MQ classes for JMS do not invoke a message-driven bean (MDB)application if the message body is zero bytes

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

  • If a message is consumed by the MQ Resource Adapter running in
    an application server and the message has no payload (there are
    no further headers and no message body after the MQMD header)
    then the message is not delivered to a message-driven bean (MDB)
    application.  In a WebSphere Application Server environment, the
    following message is logged to the SystemOut.log file:
    
      "
      CWSJY0003W: JMSCC0108: IBM MQ classes for JMS had detected
      a message, ready for asynchronous delivery to an application.
      When delivery was attempted, the message was no longer
      available. See the "Troubleshooting JMSCC0108 messages" topic
      in the IBM MQV9.0 section of IBM Knowledge Center for
      possible causes and actions.
      "
    
    The expected behavior is that the message should be delivered to
    the message-driven bean even if the the message body contains no
    data.
    

Local fix

  • This issue can be avoided by having messages that contain a
    payload that is at least 1 byte in size.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects message-driven bean (MDB) applications
    deployed into application servers, such as WebSphere Application
    Server.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an Activation Specification (or Listener Port in WebSphere
    Application Server) browsed and then destructively consumed a
    message with no payload (the message only contained an MQMD
    header), the MQ classes for JMS would not pass that message onto
    the message-driven bean (MDB) application to which it was
    associated.  This was because it incorrectly assumed that the
    message with a body of zero bytes in length was not valid and
    had already been consumed by another application.
    

Problem conclusion

  • The MQ classes for JMS have been updated to ensure that
    message-driven bean (MDB) applications are invoked even when the
    MQ message consumed has no payload.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.7
    v9.1 CD    9.1.3
    v9.1 LTS   9.1.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

    IT27995

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-05

  • Closed date

    2019-02-19

  • Last modified date

    2019-02-19

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 February 2019