IBM Support

IT38312: Missing trace while processing secure socket read and write, andSIGSEGV memory exception

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • SIGSEGV memory exception and missing trace in amqrmppa process.
    
    Call stack from the failure data capture (FDC) generated by the
    process contains lines similar to these:
    
    /opt/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+n)
    /lib64/libpthread.so.0(+n)
    :
    :
    /opt/mqm/lib64/libmqmr_r.so(cciTcpSslWriteCallback+n)
    :
    :
    /opt/mqm/lib64/libmqmr_r.so(ccigsk_secure_soc_read+n)
    /opt/mqm/lib64/libmqmr_r.so(cciSslSecureReceive+n)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Queue managers that serve client application programs over
    TCP/IP using TLS secured connections.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    After reading data from the client, the secure sockets code
    (GSKit) on the MQ server behaves normally by calling back into
    MQ code to send data to the network, to perform some
    handshaking.  The MQ code uses the wrong thread context to write
    trace, resulting in the trace being written in the wrong place,
    and in the worst case a memory exception (SIGSEGV) may occur.
    This happens in the amqrmppa process.
    

Problem conclusion

  • The IBM MQ code has been corrected to avoid using the wrong
    thread context.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.10
    v9.x CD    9.2.5
    
    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

    IT38312

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-09

  • Closed date

    2021-11-25

  • Last modified date

    2021-11-25

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
26 November 2021