IBM Support

IT16300: MQ-JMS: Provide additional information to assist users with understanding causes of the JMSCC0108 message

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using activation specifications or the WebSphere MQ
    messaging provider included with WebSphere Application Server,
    messages containing the text:
    
    JMSCC0108: An attempt to get a message for delivery to an
    message listener was made, but the message was not there.
    
    occasionally appear in the application server log files.  It is
    not clear what this message means, or what action needs to be
    taken by the user to prevent it from occurring.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects two categories of users:
    
    Category 1:
    ---------------
    Users of:
    
    - The WebSphere MQ V7.1 resource adapter.
    - The WebSphere MQ V7.5 resource adapter.
    - The IBM MQ V8 resource adapter.
    - The IBM MQ V9 resource adapter.
    
    who have activation specifications that are configured to
    monitor JMS destinations for messages.
    
    Category 2:
    ---------------
    Users of:
    
    - The WebSphere Application Server V8.5.5 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V9.0 MQ messaging provider.
    
    who have activation specifications or listener ports that are
    configured to monitor JMS destinations for messages.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an activation specification or WebSphere Application Server
    listener port has been configured to monitor a JMS destination
    for messages, the following steps are carried out:
    
    - The activation specification or listener port connects to the
    queue manager, and browses the JMS destination for messages.
    - When a message is detected, an internal message reference is
    constructed that represents that message.
    - A server session is obtained from the server session pool
    associated with the activation specification or listener port.
    - The message reference is loaded into the server session.
    - The server session is started on a new thread.
    - The activation specification or listener port then browse the
    destination again, looking for the next message to process.
    
    When the server session starts, it will:
    
    - Start an XA transaction or a local transaction, as required.
    - Issue a destructive MQGET call to get the message mentioned in
    the message reference.
    - Pass the message to an instance of a message-driven bean's
    onMessage() method for processing.
    - Complete the transaction, once the onMessage() method has
    completed.
    - Return itself to the activation specification or listener
    port's server session pool.
    
    If there is a delay in between:
    
    - The activation specification or listener port browsing the
    message.
    - The server session thread issuing the destructive MQGET API
    call to get the message.
    
    then it is possible that the message which was detected is no
    longer on the destination when the server session tries to get
    it, either because the message has expired or has been processed
    by another activation specification or listener port. In this
    situation, a message containing the text:
    
      JMSCC0108: An attempt to get a message for delivery to an
    message listener was made, but the message was not there.
    
    was reported in the application server's log files. This message
    was not very informative, and did not contain any details about
    what action to take to prevent it from occurring in the future.
    

Problem conclusion

  • A new topic:
    
    Troubleshooting JMSCC0108 messages
    
    has been added to the WebSphere MQ V7.1 and V7.5, and the IBM MQ
    V8.0 and V9.0, sections of IBM Knowledge Center. This topic
    describes why the JMSCC0108 messages are reported, along with
    the actions that can be taken to prevent them from occurring.
    
    In addition to this, the text of the JMSCC0108 message has now
    been updated to contain a reference to this topic. The new text
    for the message is shown below:
    
    WebSphere MQ V7.1:
    ------------------------------
    JMSCC0108: WebSphere 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 WebSphere MQ
    V7.1 section of IBM Knowledge Center for possible causes and
    actions.
    
    WebSphere MQ V7.5
    -------------------------------
    JMSCC0108: WebSphere 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 WebSphere MQ
    V7.5 section of IBM Knowledge Center for possible causes and
    actions.
    
    IBM MQ V8.0:
    -------------------------------
    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 MQ V8.0
    section of IBM Knowledge Center for possible causes and actions.
    
    IBM MQ V9.0:
    ------------------------------
    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 MQ V9.0
    section of IBM Knowledge Center for possible causes and actions.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.9
    v7.5       7.5.0.9
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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

    IT16300

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-26

  • Closed date

    2017-06-22

  • Last modified date

    2017-06-22

  • 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":"BU029","label":"Software"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}]}]

Document Information

Modified date:
25 May 2020