IBM Support

IV50249: A JMS APP REQUESTS A DYNAMIC QUEUE SPECIFYING AN ASTERISK IN THE QMGR NAME, THE CONNECT IS SUCCESSFUL BUT THE MQOPEN FAILS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ JMS client application which uses a client
    channel definition table (CCDT) may connect using an asterisk as
     the first character of the queue manager name, for example
    "*MY.QMGR".  However, any attempt to open a dynamic queue on the
     connection will fail with an exception like:
    
    ABC.JMSWMQ2008: Failed to open MQ queue
    'SYSTEM.DEFAULT.MODEL.QUEUE'.:com.ibm.mq.MQException:
    JMSCMQ0001: WebSphere MQ call failed with compcode '2'
    ('MQCC_FAILED') reason '2086' ('MQRC_UNKNOWN_OBJECT_Q_MGR')
    

Local fix

  • This issue can be avoided by not using a CCDT or by not
    specifying an asterisk in the Queue Manager name.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ classes for JMS
    who are
    attempting to create a temporary
    dynamic queue on a connection generated from a CCDT, where the
    entry in the CCDT was selected as part of a queue manager group
    by using a '*' character in the queue manager name
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    When the temporary queue was created, a model queue was opened
    on the queue manager, passing some options. One of these was the
    queue manager name. However, the queue manager name that was
    being passed was the queue manager group name set on the
    connection factory containing the '*' character
    rather than the actual name of the queue manager connected to.
    This is not a known queue manager name, hence the
    MQRC_UNKNOWN_OBJECT_Q_MGR
    

Problem conclusion

  • The WebSphere MQ classes for JMS have been modified such that
    when the model queue is opened, the queue manager name passed to
    the queue manager in
    the open options structure is the resolved name of the queue
    manager, which is a
    known queue manager name.
    
    ---------------------------------------------------------------
    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
    
    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

    IV50249

  • Reported component name

    WMQ LIN X86 V7

  • Reported component ID

    5724H7224

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-01

  • Closed date

    2013-11-29

  • Last modified date

    2013-11-29

  • 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 LIN X86 V7

  • Fixed component ID

    5724H7224

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022