PI32255: VERSIONINFO.SH AND HISTORYINFO.SH FAILING TO PROCESS HISTORY.XML FILE

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• versionInfo.sh and historyInfo.sh failing to process
  history.xml file.
  

Local fix

• Workaround provided.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users are not able to create            *
  *                      profiles. Scripts bin/historyInfo.sh    *
  *                      and bin/versionInfo.sh fail to show     *
  *                      correct information.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is rare because it is caused by a corrupt
  Installation Manager history.xml and that should never happen.
  When reading the corrupt history.xml, the historyInfo.sh will
  issue a NullPointerException and quit. This exception causes
  profile utilities and versionInfo.sh to exit abnormally and
  then fail to create the profile and show the correct WebSphere
  Application Server version.
  

Problem conclusion

• The fix is to check the pointer. If it is null then skip the
  code and avoid the exception.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.5.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP