IBM Support

PI06508: JMS APPLICATION IN BINDING MODE CONNECTIONS CONNECTING TO QUEUE SHARING GROUP (QSG) CAN CONNECT TO DIFFERENT QMGRS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JMS application in Binding mode connections
    connecting use Queue Sharing Group Name (QSG) can
    connect to different QMGRs, when they should
    all connect to the same queue manager
    
    ...
    Additional Symptom(s) Search Keyword(s):
    .
    The doc shows that the MDB is failing when
    attempting to issue MQCB on a new worker thread
    (id 25), due to the handle passed being invalid.
    The handle was created prior to the worker thread
    starting, when thread 5 opened the queue.
    The problem appears to be that thread 5 was
    connected to qmgr 1, however thread 25 was
    connected to qmgr 2, and so the handle did not
    exist on qmgr 1.
    .
    Trace: 2013/11/18 12:22:27.014 01 t=9C0988 c=UNK
    key=S2 (13007002)
    ThreadId: 00000025
    FunctionName:
    Java_com_ibm_mq_jmqi_local_internal_base_Native_MQCB
    (Java_com_ibm_mq_jmqi_local_internal_base_Native_MQCB)
    SourceId:
    Java_com_ibm_mq_jmqi_local_internal_base_Native_MQCB
    Category: FINER
    ExtendedMessage: Exit; 2019
    ,
    Trace: 2013/11/18 12:22:27.041 01 t=9C0988 c=UNK
    key=S2 (13007002)
    ThreadId: 00000025
    FunctionName: CLASS NAME NOT AVAILABLE
    SourceId: CLASS NAME NOT AVAILABLE
    Category: FINEST
    ExtendedMessage: (CLASS NAME NOT AVAILABLE)
    JmqiWorkerThread: run(); run() method about to run job
    .
    and
    .
    Java Vendor      :- IBM Corporation
    Java Version     :- 2.4
    Source Class     :- WMQMessageConsumer
    Source Method    :- checkJmqiCallSuccess
    ProbeID          :- XN004001
    Thread           :- name=WebSphere t=009bc230
       priority=5 group=main ccl=com.ibm.ws.bootstrap.
       ExtClassLoader@4c624c62
                                          Data
                                          ----
    |   XMSC_DESTINATION_NAME  :-  QUEUE1
    |   compcode               :-  2
    |   hconn                  :-  0x3af56c18
    |   messageid              :-  JMSWMQ0020
    |   reason                 :-  2019
                               Version information
                               -------------------
    .
    
    Trace: 2013/11/18 12:21:26.879 01 t=9BC230 c=UNK
    key=S2 (13007002)
    ThreadId: 00000019
    FunctionName:
    com.ibm.ejs.jms.listener.WS390ConnectionBrowserWrapper
    SourceId:
    com.ibm.ejs.jms.listener.WS390ConnectionBrowserWrapper
     Category: AUDIT
     ExtendedMessage:
     BBOJ0094E: MDB MyMDB#MyMDB.jar#
     FeeMessageListener REGISTRATION FAILED - CAUSE: j
    .jms.JMSException: JMSCS0006: An internal problem occurred.
    Diagnostic information for service was written to 'null'.
    the application as the product is in an inconsistent
    internal state.
    .at com.ibm.msg.client.commonservices.trace.Trace.ffst
     (Trace.java:1540)
    .at com.ibm.msg.client.wmq.internal.WMQMessageConsumer.
     checkJmqiCallSuccess(WMQMessageConsumer.java:121)
    .at com.ibm.msg.client.wmq.internal.WMQAsyncConsumerShadow.
     registerMessageListener(WMQAsyncConsumerShadow.java:841)
    .at com.ibm.msg.client.wmq.internal.WMQConnectionBrowser.
     <init>(WMQConnectionBrowser.java:1318)
    .at com.ibm.msg.client.wmq.internal.WMQConnection.
     createConnectionBrowser(WMQConnection.java:900)
    .at com.ibm.msg.client.jms.internal.JmsConnectionImpl.
     createConnectionBrowser(JmsConnectionImpl.java:902)
    .at com.ibm.mq.jms.MQConnection.
     reateConnectionBrowser(MQConnection.java:136)
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Errors using MDBs that connect in       *
    *                      bindings mode to a queue sharing group. *
    *                      Errors include:                         *
    *                       MDB fails to register                  *
    *                       MQRC_HOBJ_ERROR (2019) when MQCB is    *
    *                        called                                *
    *                       5C6-00940024 in CSQMCTXE               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the first bindings mode connection is made by a WebSphere
    Application Server region using the queue sharing group name, a
    connection is made to a random active queue manager in the queue
    sharing group.
    When the same region makes subsequent connections, these should
    connect to the same queue manager, unless that queue manager is
    no longer available, however this was not occurring when
    connecting to MQ V710 queue managers, and so subsequent
    connections would also choose a random active queue manager to
    connect to.
    If a subsequent connection was for a related task e.g. a worker
    thread, and connected to a different queue manager than the
    initial connection, errors such as those reported can occur.
    

Problem conclusion

  • CSQBCON is changed to correctly pass the preferred queue manager
    to connect to into identify processing.
    100Y
    CSQBCON
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI06508

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-11-19

  • Closed date

    2013-11-29

  • Last modified date

    2014-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI13092

Modules/Macros

  • CSQBCON
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI13092

       UP13/12/24 P F312 Ž

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 January 2014