IBM Support

IT34691: MQ Appliance power outage may result in the MQ Web Console reporting 'Error 500: Internal error'

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

  • As part of a failure test, the power cables from the MQ
    Appliance were unplugged. When reconnected and the appliance
    became online, connectivity via SSH and WebGUI was working,
    however, the MQ Web Console inside the WebUI was showing below
    error:
    
    Error 500: Internal error
    

Local fix

  • Rebooting the MQ Appliance will resolve this.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    The issue impacts users of the MQ Appliance who are utilising
    the MQ Web Console/MQ Rest API.
    
    
    Platforms affected:
    Linux on x86-64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    On the MQ Appliance, when there was an abrupt abnormal end of
    the MQ Web Console/RestAPI, such as in the case of a system
    power outage, then once the appliance had been restarted the MQ
    Web Console was generating the following error message when an a
    web browser attempted to access it:
    
    The returned HTTP status is 500 Error
    
    The MQ Web Console Server console.log contained the following
    message:
    
    JVMSHRC091E Read corrupt data for item 0x00007FA8628964BC
    (invalid dataType)
    JVMDUMP039I Processing dump event "corruptcache", detail "" at
    2020/10/21 07:17:39 - please wait.
    JVMDUMP032I JVM requested System dump using
    '/opt/ibm/wlp/usr/servers/defaultServer/core.20201021.071739.108
    79.0001.dmp' in response to an event
    Warning: unable to move dump to
    "/opt/ibm/wlp/usr/servers/defaultServer/core.20201021.071739.108
    79.0001.dmp" across file systems (check kernel core_pattern).
    Using alternate file location
    "/var/mqm/diag/core.20201021.071739.10879.0001.dmp"
    JVMDUMP010I System dump written to
    /var/mqm/diag/core.20201021.071739.10879.0001.dmp
    JVMDUMP032I JVM requested Java dump using
    '/opt/ibm/wlp/usr/servers/defaultServer/javacore.20201021.071739
    .10879.0002.txt' in response to an event
    JVMDUMP010I Java dump written to
    /opt/ibm/wlp/usr/servers/defaultServer/javacore.20201021.071739.
    10879.0002.txt
    JVMDUMP032I JVM requested Snap dump using
    '/opt/ibm/wlp/usr/servers/defaultServer/Snap.20201021.071739.108
    79.0003.trc' in response to an event
    JVMDUMP010I Snap dump written to
    /opt/ibm/wlp/usr/servers/defaultServer/Snap.20201021.071739.1087
    9.0003.trc
    JVMDUMP013I Processed dump event "corruptcache", detail "".
    JVMSHRC442E Shared cache "liberty-mqsystem" is corrupt.
    Corruption code is -3. Corrupt value is 0x00007FA8628964BC. No
    new JVMs will be allowed to connect to the cache.
     	Existing JVMs can continue to function, but cannot update
    the cache.
    

Problem conclusion

  • The MQ Web Console/MQ Rest API code has been updated to prevent
    the issue from occurring.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.7
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.2
    
    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

    IT34691

  • Reported component name

    MQ APPLIANCE M2

  • Reported component ID

    5737H4700

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-27

  • Closed date

    2020-11-05

  • Last modified date

    2020-11-05

  • 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

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

Document Information

Modified date:
06 November 2020