IBM Support

IC63260: WEBSPHERE MQ CLIENT APPLICATION IS NOT ABLE TO CONNECT TO THE QUEUE MANAGER AFTER MIGRATION MQ V7.0.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ client application that was able to connect to
    the queue manager at MQ version 6.0 is not able to connect to
    the queue manager after it was migrated to version 7.0.
    
    The application connection attempt results in AMQ6119 error
    messages in the WebSphere MQ general error log. There is an FDC
    generated for the application process to report probe id
    XC130031 due to an Access Violation at address xxxxxxxxx when
    reading. The MQM Function Stack shows:
    
    reqDoConnect
    reqDuplicateCno
    xcsFFST
    
    This problem occurs because the client application specifies
    the version of the MQ connect options (MQCNO) structure as
    MQCNO_VERSION_2 and they are using the fields SSLConfigPtr and
    SSLConfigOffset which are valid only in versions of MQCNO
    greater than or equal to MQCNO_VERSION_4. The use of
    SSLConfigPtr was being ignored in WebSphere MQ v6. Although the
    WebSphere MQ v7 code checks for SSLConfigPtr and
    SSLConfigOffset correctly, it has incorrect behavior with
    respect to verification of the version of MQCNO and it will
    result in the Access Violation.
    
    ADDITIONAL KEYWORDS: SSL secure sockets layer HCONN MQCONN
    

Local fix

  • If the application use of SSLConfigPtr / SSLConfigOffset is
    intentional then modify the application to specify the version
    of the MQCNO structure as MQCNO_VERSION_4 or higher.
    If the use of SSLConfigPtr/SSLConfigOffset is not intentional,
    then initialize the MQCNO structure to MQCNO_DEFAULT before
    using it in the application.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere MQ C applications who specify
    MQCNO_VERSION_4 and less and use SSLConfigPtr / SSLConfigOffset.
    
    Users of WebSphere MQ C applications who specify
    MQCNO_VERSION_2 and less and use ClientConnPtr /
    ClientConnOffset.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    WebSphere MQ applications that specified non-zero values for
    SSLConfigPtr or SSLConfigOffset and set the version of MQCNO to
    less than MQCNO_VERSION_4 received illegal memory access
    exceptions because there was no check in place to validate the
    version of MQCNO before using SSLConfigPtr and SSLConfigOffset.
    
    Similarly, applications that specified non-zero values for
    ClientConnPtr or ClientConnOffset and set the version of MQCNO
    to less than MQCNO_VERSION_2 received illegal memory access
    exception.
    

Problem conclusion

  • A check was introduced to validate the version of MQCNO in use
    before making use of SSLConfigPtr, SSLConfigOffset,
    ClientConPtr or ClientConnOffset.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.1
    --------           --------------------
    Windows            U200310
    AIX                U827232
    HP-UX (PA-RISC)    U826485
    HP-UX (Itanium)    U826884
    Solaris (SPARC)    U827125
    Solaris (x86-64)   U827374
    iSeries            tbc_p700_0_1_1
    Linux (x86)        U826321
    Linux (x86-64)     U827231
    Linux (zSeries)    U827105
    Linux (Power)      U826779
    
    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

    IC63260

  • 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-09-18

  • Closed date

    2009-10-30

  • Last modified date

    2009-11-24

  • 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:
24 November 2009