IBM Support

IC60100: WEBSPHERE MQ V7 JMS APPLICATIONS USING RECEIVENOWAIT() WILL FAIL TO PROCESS MORE THAN ONE MESSAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ Version 7 Java Message Service (JMS) applications
    that call the method:
    
    MessageConsumer.receiveNoWait()
    
    fail to process more than one message on the Destination being
    monitored. Once the first message is retrieved, the JMS Session
    being used by the MessageConsumer will be stopped and never
    restarted.
    
    A trace taken when the application fails to get a message shows
    the following:
    
    (com.ibm.msg.client.wmq.v6.jms.internal.MQXASession)
    isStopped(): getter true
    (CLASS NAME NOT AVAILABLE)
    unspecified method: early return. ProviderSession closed
    and timeOut = 0
    

Local fix

  • A trace of the problem shows the first receiveNoWait() call
    happens successfully and the session and connection are closed
    (i.e returned back to the pool). In the second receiveNoWait()
    call, the same session is retrieved from the pool but this
    session seems to be in the stop state.
    .
     10/02/09 11:14:59:590 EST  00000006 MQXASession   3
    (com.ibm.msg.client.wmq.v6.jms.internal.MQXASession)
    (com.ibm.msg.client.wmq.v6.jms.internal.MQXASession)
     :/6d146d14
    isStopped(): getter
    .                                 true
     10/02/09 11:14:59:590 EST  00000006 CLASS NAME NO 3
    (CLASS NAME NOT AVAILABLE)  :/79d979d9  unspecified method:
    early return.
    ProviderSession closed and timeOut = 0
                                     <null>
    .
    Because the session was in STOP state no further messages
    were retrived by the application.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects WebSphere MQ Version 7 Java Message Service
    (JMS) applications that get messages from a JMS Destination
    using the method MessageConsumer.receiveNoWait().
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    Due to the redesign of the code that took place in WebSphere MQ
    Version 7, once a JMS Session was stopped following a call to
    receiveNoWait(), there was no way to restart it again.
    

Problem conclusion

  • The MQXASession class has been modified to methods which are
    used to restart JMS Sessions that have been stopped.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.0.2
    --------           --------------------
    Windows            U200302
    AIX                U822354
    HP-UX (PA-RISC)    U822349
    HP-UX (Itanium)    U822351
    Solaris (SPARC)    U822353
    Solaris (x86-64)   U822394
    iSeries            tbc_p700_0_0_2
    Linux (x86)        U822348
    Linux (x86-64)     U822393
    Linux (zSeries)    U822352
    Linux (Power)      U822350
    
    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

    IC60100

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-19

  • Closed date

    2009-03-20

  • Last modified date

    2009-04-20

  • 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

  • R700 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":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 April 2009