IBM Support

IT04811: IN WEBSPHERE MQ 7.5.0.1 FDCS THROWN WITH THE FOLLOWING PROBEIDS XC130003 & XY348060 THIS COULD LEAD TO A POTENTIAL MQ HANG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While running with WebSphere MQ 7.5.0.1 the following FDCs are
    thrown
    ...
    Probe Id :- XC130003
    Application Name :- MQM
    Component :- xehExceptionHandler
    Program Name :- java
    Major Errorcode :- STOP
    Minor Errorcode :- OK
    Probe Type :- HALT6109
    Probe Severity :- 1
    Probe Description :- AMQ6109: An internal WebSphere MQ error
    has occurred.
    Arith1 :- 11 (0xb)
    Comment1 :- SIGSEGV: invalid address permissions(118)
    .
    MQM Function Stack
    xtmTimerThread
    xcsInitialize
    xcsConnectExistingSharedSubpool
    xlsThreadInitialization
    xlsThreadPreInitialization
    xcsAllocateQuickCell
    xstQuickCellExtendBlock
    xcsAllocateMemBlock
    xcsSubtaskExtendSet
    xcsResetEventSem
    xlsResetEvent
    xcsFFST
    ...
    Probe Id :- XY348060
    Application Name :- MQM
    Component :- xtmStartTimerThread
    Program Name :- java
    Major Errorcode :- OK
    Minor Errorcode :- OK
    Probe Type :- INCORROUT
    Probe Severity :- 4
    Probe Description :- AMQ6125: An internal WebSphere MQ error
    has occurred.
    FDCSequenceNumber :- 1
    .
    MQM Function Stack
    MQCONNX
    zswGetEntryPointsByName
    MQCONNX
    zstMQCONNX
    zstMQConnect
    ziiMQCONN
    ziiConnectToAgent
    ziiStartAgent
    zcpReceiveOnPipe
    xcsWaitEventSem
    xlsWaitEvent
    xtmRequestCallback
    xtmStartTimerThread
    xcsFFST
    ...
    This could lead a WMQ Queue manager hanging.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM MQ
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Potentially illegal sequence of calls to common services if MQ
    exhausts a shared memory set while a thread not running under
    the mqm account is initializing common services.
    

Problem conclusion

  • The code has been corrected to eliminate the invalid common
    services usage.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.5
    v8.0       8.0.0.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

    IT04811

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-08

  • Closed date

    2014-12-17

  • Last modified date

    2015-11-18

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
25 September 2021