IBM Support

IT39514: Application crashes due to sigsegv when connecting to default queue manager

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

  • Connection to a default queue manager by a client application
    fails and crashes with sigsegv
    .
    | Probe Id          :- XC130031
    | Application Name  :- MQM
    | Component         :- xehExceptionHandler
    | Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
    | Minor Errorcode   :- OK
    | Probe Type        :- MSGAMQ6119
    | Probe Severity    :- 1
    | Probe Description :- AMQ6109S: An internal IBM MQ error has
      occurred.
    | FDCSequenceNumber :- 0
    | Comment1          :- Access Violation at address 00000000
        when reading
    
    An Unhandled Exception detected in process 10010, on thread
    0x34E4.
    Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
    Address: 0023:6057B1C0.
    The thread could not read from memory address 0x00000000.
    
    MQM Function Stack
    MQCONNX
    zswGetEntryPointsByName
    MQCONNX
    trmzstMQCONNX
    zstMQCONNX
    zstMQConnect
    zutObtainDefaultQMName
    xcsBrowseIniCallback
    xcsBrowseFileCallback
    zutDefQMCallback
    xcsFFST
    

Local fix

  • A blank line after the "DefaultQueueManager:" stanza line of the
    mqs.ini file is the trigger condition for the issue
    issue. Ensure there is no blank line after the
    "DefaultQueueManager:" stanza to avoid the sigsegv.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users connecting to a default queue manager
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A programming error meant that an invalid variable access was
    made when reading default queue manager name from mqs.ini file
    

Problem conclusion

  • The MQ code has been corrected to prevent the incorrect variable
    access when reading default queue manager name from mqs.ini file
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.6
    v9.x CD    9.3.0.0
    
    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

    IT39514

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-12-29

  • Closed date

    2022-03-17

  • Last modified date

    2022-04-13

  • 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

[{"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":"920"}]

Document Information

Modified date:
14 April 2022