IBM Support

IT43783: MQ processes and commands might fail if the qm.ini file containsunexpected character and MQ trace is enabled

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

  • An unexpected character in the qm.ini file when MQ tracing is
    turned on for the Queue Manager
    caused crash of amqrmppa and runmqchl processes affecting
    stability of MQ Queue Manager.
    The issue might also affect other MQ processes and also
    commands(e.g. strmqm).
    
    FDC generated by runmqchl:
    
    Component         :- xehExceptionHandler
    Program Name      :- runmqchl
    Major Errorcode   :- STOP
    Probe Type        :- HALT6109
    Probe Severity    :- 1
    Probe Description :- AMQ6109S: An internal IBM MQ error has
    occurred.
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped((nil))
    
    O/S Call Stack for current thread
    /opt/mqm/lib64/libmqmcs_r.so(+0x1058af)[0x7ff1180ed8af]
    /opt/mqm/lib64/libmqmcs_r.so(+0x1293aa)[0x7ff1181113aa]
    /opt/mqm/lib64/libmqmcs_r.so(+0x128383)[0x7ff118110383]
    /opt/mqm/lib64/libmqmcs_r.so(xcsFFSTFn+0x20eb)[0x7ff11811351b]
    /opt/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+0x6c9)[0x7ff118
    1050e9]
    /usr/lib64/libpthread.so.0(+0x12dd0)[0x7ff11782add0]
    /opt/mqm/lib64/libmqmcs_r.so(+0x2296a2)[0x7ff1182116a2]
    /opt/mqm/lib64/libmqmcs_r.so(+0x229a81)[0x7ff118211a81]
    /opt/mqm/lib64/libmqmcs_r.so(xcsBrowseIniCallback+0x1df)[0x7ff11
    8201d4f]
    /opt/mqm/lib64/libmqmcs_r.so(+0x16b01c)[0x7ff11815301c]
    /opt/mqm/lib64/libmqmcs_r.so(xeiGetTuningParameters+0xe4)[0x7ff1
    18154ec4]
    /opt/mqm/lib64/libmqmcs_r.so(xcsDisplayMessageForError+0x28e)[0x
    7ff1180f9fbe]
    /opt/mqm/lib64/libmqmr_r.so(rrxReportError+0x6cd)[0x7ff118fed8ad
    ]
    /opt/mqm/lib64/libmqmr_r.so(rriCallerEntry+0x7ac)[0x7ff118eefd7c
    ]
    /opt/mqm/bin/runmqchl[0x40139d]
    /usr/lib64/libc.so.6(__libc_start_main+0xf3)[0x7ff1172756a3]
    /opt/mqm/bin/runmqchl[0x401409]
    
    MQM Function Stack
    rriCaller
    rriCallerEntry
    rrxReportError
    xcsDisplayMessageForError
    xeiGetTuningParameters
    xeiReadConfig
    xcsBrowseIniCallback
    xusReadSingleStanza
    xusAddStanzaLineList
    xcsFFST
    
    FDC generated by strmqm:
    
    Probe Id          :- XC130003
    Component         :- xehExceptionHandler
    Program Name      :- strmqm
    Arith1            :- 11 (0xb)
    Comment1          :- SIGSEGV: address not mapped((nil))
    
    O/S Call Stack for current thread
    /opt/mq9206/lib64/libmqmcs_r.so(+0x10589f)[0x7f4fe1acc89f]
    /opt/mq9206/lib64/libmqmcs_r.so(+0x12925a)[0x7f4fe1af025a]
    /opt/mq9206/lib64/libmqmcs_r.so(+0x128233)[0x7f4fe1aef233]
    /opt/mq9206/lib64/libmqmcs_r.so(xcsFFSTFn+0x20eb)[0x7f4fe1af23cb
    ]
    /opt/mq9206/lib64/libmqmcs_r.so(xehExceptionHandler+0x6c9)[0x7f4
    fe1ae40d9]
    /usr/lib64/libpthread.so.0(+0xf630)[0x7f4fe040d630]
    /opt/mq9206/lib64/libmqmcs_r.so(+0x228d92)[0x7f4fe1befd92]
    /opt/mq9206/lib64/libmqmcs_r.so(+0x229171)[0x7f4fe1bf0171]
    /opt/mq9206/lib64/libmqmcs_r.so(xcsBrowseIniCallback+0x1df)[0x7f
    4fe1be05ff]
    /opt/mq9206/lib64/libmqml_r.so(zslStartQM+0x13e9)[0x7f4fe26321c9
    ]
    strmqm[0x400b49]
    /usr/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f4fdfe4e555]
    strmqm[0x400bb7]
    
    MQM Function Stack
    xcsBrowseIniCallback
    xusReadSingleStanza
    xusAddStanzaLineList
    xcsFFST
    

Local fix

  • Find and remove the unexpected character from qm.ini and restart
    queue manager.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users enabling MQ trace when the qm.ini file contains an
    unexpected character.
    
    
    Platforms affected:
    AIX, Linux on x86-64, Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in validating the stanzas in the qm.ini file caused a
    memory exception and resulted in a failure of the MQ process or
    command if trace was enabled.
    

Problem conclusion

  • MQ code has been modified to resolve the issue in validating the
    stanzas in the qm.ini file.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.20
    v9.3 LTS   9.3.0.10
    v9.x CD    9.3.4
    
    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

    IT43783

  • 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

    2023-05-18

  • Closed date

    2023-08-01

  • Last modified date

    2023-08-01

  • 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:
01 August 2023