IBM Support

IV47311: WEBSPHERE MQ CLASSES FOR JAVA/JMS ATTEMPT TO CREATE MORE SHARED CONVERSATIONS THAN THE CONFIGURED SHARECNV LIMIT ON A CONNECTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A channel has defined SHARECNV(10) and the client is trying to
    start an 11th conversation.
    
    At the z/OS qmgr we receive:
    CSQX504E -XGA1 CSQXRESP Local protocol error,
    channel GXPEKA01CL.TO.MQAX
    type=00000023 data=0000000B
    
    The CSQX504E with type 00000023 (rfpERR_MAX_CONVS_EXCEEDED) is
    being issued as the client is trying to start a new
    conversation, when the maximum number of conversations has
    already been reached.
    
    On distributed platforms an FDC with Probe Id
    RM557001 is seen with  with following information:
    
    | Major Errorcode   :- rrcE_PROTOCOL_ERROR
    | Minor Errorcode   :- OK
    | Probe Type        :- MSGAMQ9504
    | Probe Severity    :- 2
    | Probe Description :- AMQ9504: A protocol error was detected
    for channel ''. |
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ classes for JMS 7.0.1 client.
    - The WebSphere MQ V7.0.1 Resource Adapter.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    
    that are using multiplexed connections to the WebSphere MQ Queue
    Manager.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    A client application attempted to make a number of connections
    to the queue manager using a multiplexing enabled connection
    (SHARECNV >= 1). The number of concurrent threads attempting to
    obtain a connection was greater than the number of conversations
    supported on the connection.
    
    Due to the number of concurrent threads a timing window was
    encountered which caused the number of conversations created on
    the WMQ client side to be greater than the number of
    conversations allowed on the channel.
    

Problem conclusion

  • This APAR resolves the issue by ensuring that the number of
    conversations created on the client side is less than or equal
    to the maximum number of conversations allowed on the channel.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IV47311

  • Reported component name

    WMQ LIN X86 V7

  • Reported component ID

    5724H7224

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-08-21

  • Closed date

    2013-09-12

  • Last modified date

    2015-09-22

  • 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

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

Document Information

Modified date:
08 March 2021