IBM Support

IC86134: WMQ JMS 7.5: WHEN CREATING TEMPORARYQUEUES WHILE USING ASF, RECEIVING JMS EXCEPTION '2500' ('MQRC_HCONN_ASYNC_ACTIVE')

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using WebSphere MQ classes for JMS V7.5, a temporary
    queue cannot be created while the associated JMS Connection is
    also being used by ASF ConnectionConsumers.
    
    On a newly created JMS Session (different from the one being
    used by the ASF ConnectionConsumer), and then try to create a
    temporary queue with it, the following error is received:
    
    JMSWMQ2008: Failed to open MQ queue 'SYSTEM.DEFAULT.MODEL.QUEUE'
    JMSCMQ0001: WebSphere MQ call failed with compcode '2'
    ('MQCC_FAILED')
    reason '2500' ('MQRC_HCONN_ASYNC_ACTIVE').
    

Local fix

  • None <br/>
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere MQ classes for JMS V7.5, where an
    application is attempting to create a temporary queue using a
    JMS Session which was created from a JMS Connection which
    has one or more other Sessions being used for ASF message
    consumption.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    Due to the way the WebSphere MQ V7 classes for JMS was
    implemented with respect to the communication with JMS
    Connections and Sessions with the queue manager, when a JMS
    Connection had a Session which was being actively used by ASF
    ConnectionConsumers, when a new Session attempted to create
    a temporary queue, the queue manager would return the WebSphere
    MQ return code 2500 ('MQRC_HCONN_ASYNC_ACTIVE').
    
    This was subsequently returned to the application by the
    WebSphere MQ classes for JMS with the error message:
    
    
    JMSWMQ2008: Failed to open MQ queue 'SYSTEM.DEFAULT.MODEL.QUEUE'
    
    JMSCMQ0001: WebSphere MQ call failed with compcode '2'
    ('MQCC_FAILED')
    
    reason '2500' ('MQRC_HCONN_ASYNC_ACTIVE').
    
    
    The temporary queue was not created.
    

Problem conclusion

  • The code change associated with this APAR altered the code
    so that the appropriate WebSphere MQ communication flows are
    sent when an application attempts to create a temporary queue
    where the parent JMS Connection also has a Session which is
    involved with active ASF ConnectionConsumers.
    
    This permits the temporary queue to be created by the JMS
    application.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    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

    IC86134

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-24

  • Closed date

    2012-09-28

  • Last modified date

    2012-09-28

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

  • R750 PSY

       UP

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

Document Information

Modified date:
19 September 2021