PM35902: A INVALIDLOGRECORDPARTTYPEEXCEPTION IS THROWN DURING STARTUP OF A MESSAGING ENGINE USING FILESTORE

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• During recovery, the following exception is thrown and an FFDC
  is produced:
  
  com.ibm.ws.objectManager.InvalidLogRecordPartTypeException:
  InvalidLogRecordPartTypeException_info:99
  at com.ibm.ws.objectManager.FileLogInput.readNextLogRecord
  (Unknown Source)
  at com.ibm.ws.objectManager.FileLogInput.readNext(Unknown
  Source)
  at com.ibm.ws.objectManager.ObjectManagerState.perform
  Recovery(Unknown Source)
  at com.ibm.ws.objectManager.ObjectManagerState.perform
  WarmStart(Unknown Source)
  at com.ibm.ws.objectManager.ObjectManagerState.[init]
  (Unknown Source)
  at com.ibm.ws.objectManager.ObjectManager.createObject
  ManagerState(Unknown Source)
  at com.ibm.ws.objectManager.ObjectManager.initialise
  (Unknown Source)
  at com.ibm.ws.objectManager.ObjectManager.[init]
  (Unknown Source)
  ...
  
  Other exceptions are possible but
  InvalidLogRecordPartTypeException is the most likely.  As a
  result of this the messaging engine is unable to start.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for IBM WebSphere Application Server        *
  ****************************************************************
  * PROBLEM DESCRIPTION: InvalidLogRecordPartTypeException       *
  *                      thrown during startup of a messaging    *
  *                      engine following an outage.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A highly unlikely concurrence of states inside Object Manager
  (Filestore) causes a corruption of the cyclic transaction log
  when it cycles round to the beginning of the log file.  This
  corruption would normally go unnoticed, but if at the same
  time an outage occurs, recovery does not complete because of
  the corruption.
  
  An additional problem can occur unrelated to the corruption.
  A deadlock is possible during FFDC processing.  One of the
  threads involved in the deadlock will be waiting to acquire a
  lock in FileLogOutput.print().
  

Problem conclusion

• This APAR ensures the code correctly handles the unlikely
  concurrence of states.  In addition is also resolves the
  locking hierarchy to avoid a deadlock.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.19.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  PLAT MSG COM

• Fixed component ID

  620800101

Applicable component levels

• R300 PSY

     UP