IV63397: WEBSPHERE MQ 7.0.1.7 QUEUE MANAGER IS UNRESPONSIVE AND GENERATED FDC'S WITH PROBE ID'S XC034070 AND XC302005

Fix Pack 8.0.0.1 for WebSphere MQ V8.0

APAR status

• Closed as program error.

Error description

• WMQ 7.0.1.7 queue manager becomes unresponsive and the
  following FDC's are generated:
  .
    Probe Id :- XC034070
    Component :- xcsWaitEventSem
    Program Name :- amqrmppa
    ----------------------------------------------------
    Probe Id :- XC302005
    Component :- xlsThreadTermination
    Program Name :- amqrmppa
    Major Errorcode :- STOP
    Probe Type :- HALT6109
    ----------------------------------------------------
    Probe Id :- XC476004
    Component :- xcsDecrementQuickCellUseCount
    Program Name :- amqzxma0_nd
    ----------------------------------------------------
    Probe Id :- XC307040
    Component :- xlsRequestMutex
    Program Name :- amqrmppa
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Description :- AMQ6150: WebSphere MQ semaphore
                         is busy.
    Comment1 :- OwningProcess(19136524)
                         Status(ACTIVE)
    Comment2 :- 0x00000007
    ----------------------------------------------------
  .
  The trace history for XC034070 and XC302005 shows:
  ---{ xlsGetRecoveryToken
  ----{ xcsIncrementQuickCellUseCount
  ----} xcsIncrementQuickCellUseCount rc=xecS_E_BLOCK_ALREADY_FREE
  ---} xlsGetRecoveryToken rc=OK
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All MQ users.
  
  
  Platforms affected:
  AIX, HP-UX Itanium, IBM iSeries, Linux on Power, Linux on S390,
  Linux on x86, Linux on x86-64, Linux on zSeries, Solaris SPARC,
  Solaris x86-64, Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  This is a very small timing window which can result in a
  partially initialized control block being seen by a health
  checking thread and incorrectly being cleaned up and released by
  the health checking thread. When the owning thread goes on to
  use the suspend resume area a range of issues are possible.
  
  The timing window could hypothetically be seen on any platform,
  but in practice is much more likely to occur on AIX.
  IV55876 partially closed the window at V7.0.1.8.
  The timing window exists on all MQ releases, but is even less
  likely to occur at 7.0.1.8 and later than on earlier service
  levels.
  
  In practice, this issue has only ever been observed on AIX at
  V7.0.1.7 and earlier.
  
  The problems are likely to occur during MQCONN processing, but
  it's theoretically possible that they could occur at other
  times.
  

Problem conclusion

• Defect 156233 tried to close the same window, however the code
  in that fix did not include the required serialization
  instructions.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.1.13
  v7.1       7.1.0.7
  v7.5       7.5.0.5
  v8.0       8.0.0.1
  
  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 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 AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R701 PSY

     UP