IBM Support

IC81809: Java application using C security exit that modifies ExitReason crashes

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A Java application connects as a client to a queue manager
    using a channel that is configured to use a security exit
    written in C. During the time that the application is
    connecting, the Java application crashes.
    
    MQ Explorer can crash in this way if channels that it connects
    to are configured to use security exits written in C.
    
    The failing Java application may produce a Java core file
    containing the following function on the stack:
    
    com/ibm/mq/jmqi/remote/exit/NativeExitDefinition.jniCallExit
    (NativeMethod)
    

Local fix

  • WMQ was not tolerant to a C channel exit changing the ExitReason
    code in the MQCXP structure passed to it within a Java
    process. L3 has changed the MQ code to be more robust to the
    exit changing the value of the ExitReason field.
    
    ===============================================================
    
    iFix provided by L3:
    7.1.0.0-WS-MQ-Windows-TFP79410
    http://l3.hursley.ibm.com/cgi-bin/ViewPRB.pl?5270
    
    ===============================================================
    
    As a workaround customer could try changing their security exit
    to keep the ExitReason as an input only field to see if this
    fixes their problem.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Java applications that connect to channels configured
    to use security exits written in C that modify the ExitReason
    field of the MQCXP structure passed to the exit.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The ExitReason field of the MQCXP structure passed to security
    exits is input only. Therefore the WebSphere MQ Java classes
    that call out to the security exit written in C assumed that the
    ExitReason would not be changed by the exit. If the exit does
    change the ExitReason field then on return from the exit that MQ
    Java classes access invalid data, causing the Java application
    to crash.
    

Problem conclusion

  • The MQ Java classes have now been modified not to assume that
    the ExitReason field will not be changed by a security exit.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.9
    --------           --------------------
    Windows            U200337
    AIX                U849391
    HP-UX (PA-RISC)    U849723
    HP-UX (Itanium)    U849728
    Solaris (SPARC)    U849724
    Solaris (x86-64)   U849730
    iSeries            7.0.1.9
    Linux (x86)        U849725
    Linux (x86-64)     U849729
    Linux (zSeries)    U849726
    Linux (Power)      U849727
    
                       v7.1
    Platform           Fix Pack 7.1.0.2
    --------           --------------------
    Windows            7.1.0.2
    AIX                7.1.0.2
    HP-UX (Itanium)    7.1.0.2
    Solaris (SPARC)    7.1.0.2
    Solaris (x86-64)   7.1.0.2
    iSeries            7.1.0.2
    Linux (x86)        7.1.0.2
    Linux (x86-64)     7.1.0.2
    Linux (zSeries)    7.1.0.2
    Linux (Power)      7.1.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

    IC81809

  • 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

    2012-03-06

  • Closed date

    2012-05-11

  • Last modified date

    2012-05-11

  • 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:
11 May 2012