IBM Support

IT39277: IBM MQ appliance might reload unexpectedly due to crash in apiprobe

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 IBM MQ Appliance might reload unexpectedly due to crash in
    apiprobe.
    
    Failure Notification shows
    <Date>20211122102833285CET</Date>
    <Reason>crash</Reason>
    <UploadStatus>in-progress</UploadStatus>
    <Location>temporary:///error-report.xxxxxx.20211122102833285CET.
    txt.gz</Location>
    </FailureNotificationStatus2>
    
    Around the time of the crash, the cli-log might show the
    following:
    
    cli-log:1,20211122T092818.150Z,default,cli,debug,,,0,,,0x810001f
    3,,,"(admin:default:system:*:default-config:1776):
    apic-gw-service default-gateway-peering"
    cli-log:1,20211122T092818.151Z,default,cli,debug,,,0,,,0x810001f
    4,,,"(admin:default:system:*:default-config:1790): Test: %if%
    available apic-gw-service true; continuing"
    cli-log:1,20211122T092818.151Z,default,cli,debug,,,0,,,0x810001f
    3,,,"(admin:default:system:*:default-config:1791):
    apic-gw-service"
    cli-log-b4reload:1,20211122T092737.290Z,default,cli,debug,,,0,,,
    0x810001f3,,,"(admin:default:system:*:default-config:1776):
    apic-gw-service default-gateway-peering"
    
    The decoded backtrace shows:
    
    Transaction ID: 0 (0x0000000000000000)
    Died from signal 11 (SEGV)
    Reason Hint: [Crash! Perhaps a bad ptr?]
    Referencing 0x0000000000000120 at 0x7f4038c1e39d in
    dpProperty::DelegateStack::DelegateStack(dpProperty::DelegateSta
    ck*, unsigned int, dpProperty*, dpProperty::DelegateStack*) +
    0x14d
    System Name: (unknown)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using MQ appliance
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in the internal apiprobe component caused a memory
    exception resulting in MQ appliance reload.
    

Problem conclusion

  • MQ appliance code has been modified to prevent the memory
    exception.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    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

    IT39277

  • 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

    2021-12-01

  • Closed date

    2022-02-03

  • Last modified date

    2022-06-16

  • 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

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

Document Information

Modified date:
17 June 2022