IBM Support

IT30707: MQ Appliance reloads when trying to log an event against a disabled SNMP log category

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

  • A number of logging categories are not supported on the MQ
    Appliance and they have being disabled.
    However, some of these categories are being used internally and
    a firmware reload can occur when the appliance tries to log an
    event against a disabled log category.
    
    Similar errors as below can be found on the error-report
    
    
    20190815T010857.164Z [0x80e00086][network][error] logging
    target(snmp-target): tid(1823): Cannot create connection to
    'snmp://trap/?Type=self-balancing&Level=info&Time=Wed Aug 14
    2019 21:08:47&TransID=143&Domain=default&EventCode=0x8360001e'
    20190815T010858.164Z [0x80e00062][network][error] logging
    target(snmp-target): tid(1823): Invalid log type parameter in
    'snmp://trap/?Type=self-balancing&Level=info&Time=Wed Aug 14
    2019 21:08:47&TransID=143&Domain=default&EventCode=0x8360001e'
    
    Throttler forced system reload. Reason : Low Ports.Wed Aug 14
    21:08:01 EDT 2019
    20190815T010731.065Z [0x804000a5][system][critic]
    throttle(Throttler): tid(2063): Free ports very low
    (91.470696). Throttling.
    20190815T010731.065Z [0x01a40008][system][warn]
    throttle(Throttler): tid(2063): Throttling connections due to
    low number of free ports
    

Local fix

  • Disable SNMP to avoid further reloads.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using SNMP log targets at MQ 9.1 LTS and/or 9.1.X CD
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error caused the SNMP traps to leak memory, which
    eventually caused the IBM MQ Appliance to reload.
    

Problem conclusion

  • Code changes were made to fix the memory leak caused by the SNMP
    traps
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.5
    v9.1 LTS   9.1.0.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

    IT30707

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-24

  • Closed date

    2019-12-04

  • Last modified date

    2019-12-04

  • 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 APPLIANCE M2

  • Fixed component ID

    5737H4700

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"912","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
04 December 2019