IBM Support

IT41798: MQ appliance might reload when querying queue manager or HA status or system resources status

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

  • The MQ Appliance might reload due to a watchdog restart when
    querying status of queue manager or
    High Availability(HA) or system resources using WebGUI or REST
    API. The following error was
    reported in the error report captured during reload.
    
    Thread 0x028c028d: MQ00.9.2.0.6 Platform 9006 Task main Build
    343766mq on 2022/06/16 16:32:24
    Thread 0x028c028d: 2022-08-15T08:55:18.688Z
    ...
    Thread 0x028c028d: WATCHDOG RESTART is detected.
    Thread 0x028c028d: Non-crash death_action: signum
    0x000000000000000c, si_code 0x00000000fffffffa, eip
    0x00007f6976e17d9c, si_addr 0x0000000000000000
    Thread 0x028c028d: Signal is sent by PID: 473 UID: 0 Process:
    [main]
    Thread 0x028c028d: System Name: ...
    Thread 0x028c028d: Serial: ...
    
    The decoded back trace likely to show one of the threads
    querying status of queue manager
    or HA status or system resources.
    
    WARNING: Executable start address not specified in backtrace
    Uptime: 2115277 seconds
    Transaction ID: 49771 (0x000000000000c26b)
    WATCHDOG RESTART is detected.
    Died from signal 12 (USR2)
    Reason Hint: [WATCHDOG]
    Referencing 0x0000000000000000 at 0x2bcaff5 in
    dpMqInfo::GetQueueManagersStatus(std::vector<dpMqInfo::_QmStatus
    , std::allocator<dpMqInfo::_QmStatus> >&) + 0x85
    Signal is sent by PID: 473 UID: 0 Process: [main]
    Component=xmlfirewall, Domain=default, Config=map
    Action=1, ActionName=map-match_90_304
    ...
    
    #0    0x02bcaff5 in dpMqInfo::GetQueueManagersStatus(...)
    #1    0x00ac47e7 in drQueueManagersStatus::Snapshot(...)
    #2    0x7f698329493c in dpStatusSnapshot::BuildSnapshot(...)
    #3    0x7f698329356b in dpStatusFactory::Open(...)
    #4    0x7f698356eec3 in dpMgmtStore::OpenStatusConsumer(...)
    #5    0x7f6983571cd8 in dpMgmtStore::AsXML(...)
    #6    0x00a88639 in AsyncStatusResult::Finish()
    #7    0x00f05850 in drWebGUI::GetStatus(...)
    
    WATCHDOG RESTART is detected.
    Died from signal 12 (USR2)
    Reason Hint: [WATCHDOG]
    Referencing 0x0000000000000000 at 0x7f8dceeb30fd in
    /lib64/libc.so.6 + 0xc90fd
    Signal is sent by PID: 472 UID: 0 Process: [main]
    Component=xmlfirewall, Domain=default, Config=map
    Action=1, ActionName=map-match_90_304
    ...
    
    #0    0x7f8dceeb30fd in /lib64/libc.so.6 ...
    #1    0x7f8dceee4fe8 in /lib64/libc.so.6 ...
    #2    0x02b5cc8a in dpSystemBinaryClass::launchv(...)
    #3    0x02b652cc in dpMqBinaryClass::Run(...)
    #4    0x02bcc49b in Private::dpMqInfoData::RunMq(...)
    #5    0x02bcce10 in dpMqInfo::GetApplianceHaStatus(...)
    #6    0x00ac44e6 in drMQSystemResources::Snapshot(...)
    #7    0x7f8ddc27193c in dpStatusSnapshot::BuildSnapshot(...)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using WebGUI or REST API to query status of Queue manager,
    HA or system resources in MQ appliance
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in MQ appliance lock management which manages access to
    status information caused a timeout when querying status of
    queue manager or HA or system resources resulting in appliance
    reload.
    

Problem conclusion

  • MQ appliance lock management code which manages accessing to
    status information has been modified to prevent this reload due
    to an incorrect hung process detection.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.7
    
    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

    IT41798

  • Reported component name

    MQ APPL M2002 V

  • Reported component ID

    5737H4701

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-17

  • Closed date

    2022-11-30

  • Last modified date

    2022-11-30

  • 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 APPL M2002 V

  • Fixed component ID

    5737H4701

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
01 December 2022