IBM Support

IT41035: Application terminates with FDC XC130003 due to memory exception(SIGSEGV) in TraceEntry in mqccred exit

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

  • Application unexpectedly terminates due to SIGSEGV memory
    exception in mqccred exit
    with function TraceEntry() from a non IBM MQ library at the top
    of the stack.
    
    Probe Id          :- XC130003
    Component         :- xehExceptionHandler
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped(0x1c)
    
    O/S Call Stack for current thread
    ...
    /opt/non/mq/lib/libxyz.so(TraceEntry+0x185)[0x7f0e82d73ff5]
    /var/mqm/exits64/mqccred_r(ChlExit+0x87)[0x7f0e7d0fd617]
    ...
    
    MQM Function Stack
    ImqQueueManager::connect
    MQCONN
    MQCONN
    reqDoConnect
    reqConnectChl
    rriInitSess
    rriInitExits
    rriInitExit
    rriCALL_EXIT
    xcsFFST
    
    The exit amqlcel0 might also cause the same problem.
    

Local fix

  • Change the function 'TraceEntry' name in the application if
    possible.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using mqccred or amqlcel0 exits with an application that
    uses a function called "TraceEntry".
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The IBM MQ exit mqccred was using a function with name
    "TraceEntry".  An IBM MQ application which used the mqccred
    exit was also using the same function name "TraceEntry". This
    caused a function name conflict resulting in a SIGSEGV
    in the exit and termination of the application.
    

Problem conclusion

  • IBM MQ exits mqccred and amqlcel0 have been modified to prevent
    function name conflict.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.7
    v9.3 LTS   9.3.0.2
    v9.x CD    9.3.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

    IT41035

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-25

  • Closed date

    2022-11-11

  • Last modified date

    2022-11-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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

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

Document Information

Modified date:
12 November 2022