IBM Support

SE69290: MQM400-UNPRED INTERMITTENT FDC XY396004 AMQ6035: WEBSPHERE MQ FAILED, NO STORAGE AVAILABLE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Occasional MQ FDC may be generated by user application
    attempting to connect to a local Manager. The application will
    connect after a short pause with no intervention, so no
    symptoms are usually observed beyond the FDC.
    
    Probe Id :- XY396004
    Component :- xcsAllocateMemBlock
    Major Errorcode :- xecS_E_NO_MEM
    Probe Type :- MSGAMQ6035
    Probe Description :- AMQ6035: WebSphere MQ failed, no storage
    available.
    FDCSequenceNumber :- 0
    Comment1 :- Failed to allocate memory
    
    MQM Function Stack
    MQCONN
    zswGetEntryPointsByName
    MQCONN
    zstMQCONN
    zstMQConnect
    ziiMQCONN
    ziiConnectToAgent
    xcsInitialize
    xcsConnectSharedSubpool
    xcsAttachSharedSubpool
    xlsThreadInitialization
    xlsThreadPreInitialization
    xcsAllocateQuickCell
    xstQuickCellExtendBlock
    xcsAllocateMemBlock
    xcsFFST
    
    When this occurs, other processes (user and Manager) may dump
    FDC data for Long Lock Wait:
    
    Probe Id :- XY551007
    Application Name :- MQM
    Component :- xlsSpinLockRequest
    Thread :- 00000006 SubpoolSubtask
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Type :- MSGAMQ6150
    Probe Description :- AMQ6150: WebSphere MQ resource busy.
    xcsEnumerateQuickCellBlock
    xlsSpinLockRequest
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IBM MQ users whose applications run under a profile which does
    not have MQ admin authority
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During an MQ operation, if there is a need to extend a memory
    set and the application is running under a non MQ admin profile,
    then the Execution Controller process is responsible for
    extending this set. Sometimes while extending the memory set,
    the thread waiting on this may not be made aware that the set
    has been extended and instead an xecS_E_NO_MEM FDC probe id
    XY396004 is generated.
    

Problem conclusion

  • IBM MQ code has been corrected to check that the memory set has
    been extended before generating an error AMQ6035.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.11
    v9.0 LTS   9.0.0.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

    SE69290

  • Reported component name

    IBM MQ ISERIES

  • Reported component ID

    5724H7254

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-01

  • Closed date

    2018-06-04

  • Last modified date

    2019-11-11

  • 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

    IBM MQ ISERIES

  • Fixed component ID

    5724H7254

Applicable component levels

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

Document Information

Modified date:
11 November 2019