PI18414: TRANSACTION OR RECOVERY LOG FILE MAY BECOME CORRUPT IF PROCESS DIES

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• A recovery log used by WebSphere Application Server, including
  transaction, partner, activity and compensation scope logs,
  may become corrupted if the server process dies.  The server
  is not able to start due to an exception during recovery
  indicating that the log has been marked as failed with a root
  cause most likely something related to I/O errors.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Transaction or recovery log becomes     *
  *                      corrupt and server may not able to      *
  *                      start.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is caused by a programming error in code that
  reads the recovery log but does not correctly anticipate every
  possible variation of partially written log records which can
  be present in the log file if the server ended abnormally.
  In addition, in unusual timing scenarios, log records may be
  written our of order and certain failure cases may result in
  the log records not being read during recovery.  This can
  result in transactions requiring manual completion.
  

Problem conclusion

• This APAR resolves the problem by correcting the programming
  error to ensure any incomplete log records are detected
  correctly.  In addition, if the recovery log is not shut down
  cleanly, the recovery logic anticipates that log records may
  appear later in the log.  This ensures that they are read
  during recovery given any unusual timing.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6 and 8.0.0.11.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP