IJ44683: APAR - 7.6.1.2 - MAXIMO CRASHING DUE TO DEADLOCK BLOCKED THREADS

APAR status

• Closed as program error.

Error description

• 7.6.1.2 IFIX012 - Maximo crashing due to deadlock-blocked
  threads
  
  
  Below deadlock-blocked threads can be seen in java core files
  because of which Maximo application crashes:
  
  
  1LKDEADLOCK Deadlock detected !!!
  NULL ---------------------
  NULL
  2LKDEADLOCKTHR Thread "WebContainer : 11" (0x0000000006155200)
  3LKDEADLOCKWTR is waiting for:
  4LKDEADLOCKMON sys_mon_t:0x000002C2C616BA58 infl_mon_t:
  0x000002C2C616BAD8:
  4LKDEADLOCKOBJ psdi/webclient/system/session/WebClientSessionFa
  ctory@0x00000007183E9978
  3LKDEADLOCKOWN which is owned by:
  
  2LKDEADLOCKTHR Thread "WebContainer : 13" (0x000000000648D600)
  3LKDEADLOCKWTR which is waiting for:
  4LKDEADLOCKMON sys_mon_t:0x000002C2C6158F48 infl_mon_t:
  0x000002C2C6158FC8:
  4LKDEADLOCKOBJ
  com/ibm/ws/session/store/memory/MemorySession@0x000000074EA72BB0
  
  3LKDEADLOCKOWN which is owned by:
  2LKDEADLOCKTHR Thread "WebContainer : 11" (0x0000000006155200)
  
  
  1LKDEADLOCK Deadlock detected !!!
  NULL ---------------------
  NULL
  2LKDEADLOCKTHR Thread "WebContainer : 14" (0x0000000005BDB400)
  3LKDEADLOCKWTR is waiting for:
  4LKDEADLOCKMON sys_mon_t:0x00000204D59D3FD8 infl_mon_t:
  0x00000204D59D4058:
  4LKDEADLOCKOBJ psdi/webclient/system/session/WebClientSessionFa
  ctory@0x0000000717EC8860
  3LKDEADLOCKOWN which is owned by:
  2LKDEADLOCKTHR Thread "WebContainer : 10" (0x0000000005BD8E00)
  3LKDEADLOCKWTR which is waiting for:
  4LKDEADLOCKMON sys_mon_t:0x00000204D59C37D8 infl_mon_t:
  0x00000204D59C3858:
  4LKDEADLOCKOBJ
  com/ibm/ws/session/store/memory/MemorySession@0x00000007F9B8E818
  
  3LKDEADLOCKOWN which is owned by:
  2LKDEADLOCKTHR Thread "WebContainer : 14" (0x0000000005BDB400)
  
  
  There was an APAR related to this but it was fixed in Maximo's
  much earlier version (7.5.0.x)
  https://www.ibm.com/support/pages/apar/IV50706
  
  
  App ServerIBM WebSphere Application Server 9.0.5.10
  
  Version
  Tivoli's process automation engine 7.6.1.2-IFIX20210819-1713
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-46
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
  IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB
  Build V7612-11
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
  V7611-01
  IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  V7603-32
  
  Server OSWindows Server 2019 10.0
  Server DBOracle 18.0 (Oracle Database 18c Enterprise Edition
  Release 18.0.0.0.0 - Production Version 18.3.0.0.0)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Maximo crashing due to deadlock-blocked                      *
  * threads                                                      *
  ****************************************************************
  

Problem conclusion

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels