IBM Support

IV46878: WEBSPHERE MQ CLASSES FOR JMS: MESSAGECONSUMER#RECEIVE DOES NOT RETURN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere MQ Classes for JMS 7.0.1.9,
    MessageConsumer#receive
    does not return even if the timeout has expired.
    The fact that the "receive" cannot complete because of
    the outstanding "close" means that this issue can only occur in
    a very particular circumstance. That is if:
    - A Message Consumer is used successfully, but then gets a 2009
    on Message Consumer.close.
    - A new Message Consumer is created immediately on the same
    session, and then used to receive.
    .
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ classes for JMS client.
    - The WebSphere MQ V7 Resource Adapter.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8.5 WebSphere MQ messaging
    provider.
    
    who are using JMS Message Consumers.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    A JMS application attempted to close a JMS MessageConsumer but
    this resulted in a MQRC 2009 being returned. The application
    then created a new Message Consumer from the same JMS Session
    and then called receive on that Message Consumer. The JMS
    Message Consumer receive call would then hang and not return
    even if a message was on the queue or the receive timeout had
    expired.
    
    The java stack of the hanging receive call was:
    
    Java callstack:
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:167)
    at
    com/ibm/msg/client/wmq/internal/WMQConsumerShadow.getMsg
    (WMQConsumerShadow.java:1300)
    at
    com/ibm/msg/client/wmq/internal/
    WMQSyncConsumerShadow.receiveInternal
    (WMQSyncConsumerShadow.java:239)
    at
    com/ibm/msg/client/wmq/internal/WMQConsumerShadow.receive
    (WMQConsumerShadow.java:1062)
    at
    com/ibm/msg/client/wmq/internal/WMQMessageConsumer.receive
    (WMQMessageConsumer.java:469)
    at
    com/ibm/msg/client/jms/internal/
    JmsMessageConsumerImpl.receiveInboundMessage
    (JmsMessageConsumerImpl.java:883)
    at
    com/ibm/msg/client/jms/internal/JmsMessageConsumerImpl.receive
    (JmsMessageConsumerImpl.java:546)
    at
    com/ibm/mq/jms/MQMessageConsumer.receive
    (MQMessageConsumer.java:258)
    ....
    

Problem conclusion

  • The WebSphere MQ classes for JMS have been updated to resolve
    this issue by ensuring
    that the initial failing MessageConsumer.close() call correctly
    cleans up internal state
    related to the JMS Session so that any further calls on that JMS
    Session can function correctly.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.5
    v7.0       7.0.1.12
    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

    IV46878

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-08-12

  • Closed date

    2013-10-31

  • Last modified date

    2013-12-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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 June 2020