IBM Support

IC60362: JMSEXCEPTIONS OCCUR WHEN USING THE WEBSPHERE MQ JMS PROVIDER WITH WEBSPHERE APPLICATION SERVER VERSION 7 ON Z/OS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When using the WebSphere Application Server Version 7 WebSphere
    MQ Messaging Provider to connect to WebSphere MQ for z/OS
    V7.0.0, unexpected JMSExceptions occur, and application threads
    will occasionally hang or go into a loop.
    
    For a more detailed description of the symptoms, please refer
    to the following technote:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg21376626
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ Messaging Provider
    shipped with WebSphere Application Server Version 7.
    
    Platforms affected:
     All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The WebSphere MQ Messaging Provider has two modes of operation:
    
    - WebSphere MQ Messaging Provider normal mode
    - WebSphere MQ Messaging Provider migration mode.
    
    By default, the Messaging Provider uses normal mode when
    connecting to a WebSphere MQ V7 queue manager.
    
    WebSphere MQ for z/OS V7.0.0 does not provide all the
    functionality required by normal mode connections. This results
    in failures when the Messaging Provider attempts to use a
    function that the queue manager does not support.
    

Problem conclusion

Temporary fix

Comments

  • The issue reported in this APAR will be addressed as part of
    WebSphere MQ Version 7.0.1.0.
    

APAR Information

  • APAR number

    IC60362

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-12

  • Closed date

    2009-03-17

  • Last modified date

    2009-04-02

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

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

Fix information

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:
02 April 2009