IBM Support

IC59462: WebSphere MQ v7 JMS applications may create too many, or too few shared conversations per connection.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ Java Message Service (JMS) v7 client applications
    that utilise shared
    connections may create either too many conversations per
    connection, or too few conversations before creating a new
    connection.
    
    The problem is more prevalent on systems where many JMS
    connection or JMS session objects are created at the same time.
    
    Apart from establishing too many or too few conversations per
    connection, the JMS connection and JMS Session objects operate
    normally.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users with WebSphere MQ JMS v7 client
    applications that utilise shared connections. This is the
    default mode.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    Two issues appeared to cause the symptoms:
    
    1. Multiple connection pools were created, resulting in many
    connections with low conversation counts.
    
    2. If the same pool was used, the maximum allowed
    conversations per connection was exceeded, due to a timing
    window between the creation of the conversation and the
    updating of the connection pool counters
    

Problem conclusion

  • Multiple connection pools are no longer created, and the
    connection pool counters now correctly represent the number of
    conversations for each connection.
    
    | MDVPARTL 7.0.0-WS-MQ-AixPPC64-FP0001       |
    | MDVPARTL 7.0.0-WS-MQ-HpuxIA64-FP0001       |
    | MDVPARTL 7.0.0-WS-MQ-HpuxPaRISC64-FP0001   |
    | MDVPARTL 7.0.0-WS-MQ-LinuxIA32-FP0001      |
    | MDVPARTL 7.0.0-WS-MQ-LinuxPPC64-FP0001     |
    | MDVPARTL 7.0.0-WS-MQ-LinuxS390X-FP0001     |
    | MDVPARTL 7.0.0-WS-MQ-LinuxX64-FP0001       |
    | MDVPARTL 7.0.0-WS-MQ-SolarisSparc64-FP0001 |
    | MDVPARTL 7.0.0-WS-MQ-SolarisX64-FP0001     |
    | MDVPARTL 7.0.0-WS-MQ-Windows-FP0001        |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.0.2
    
    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

    IC59462

  • 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-01-14

  • Closed date

    2009-03-13

  • Last modified date

    2013-11-19

  • 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:
19 November 2013