PI58853: LARGE INSTALLATION MANAGER HISTORY.XML FILE CAUSES OUT OF MEMORY ERROR

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.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

• After installing WebSphere Portal and starting Portal with the
  following command in a terminal:
  
  ./startServer.sh WebSphere_Portal
  
  It ends up with the following exception in the terminal:
  
  runConfigActions script execution failed. Exit code: 1
  Exception caught while waiting for runConfigActions script to
  complete: /opt/wp85/wp_profile/bin/runConfigActions.sh
  
  When manually executing runConfigActions.sh task ran OutOfMemory
  
  JVMDUMP039I Processing dump event "systhrow", detail
  "java/lang/OutOfMemoryError"
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Start some Websphere Application        *
  *                      Server commands, such as,               *
  *                      historyInfo or startServer commands,    *
  *                      in a terminal. It ends up with          *
  *                      following exception in the              *
  *                      terminal:JVMDUMP039I Processing dump    *
  *                      event "systhrow", detail                *
  *                      "java/lang/OutOfMemoryError"            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The historyInfo command generates a report that includes the
  histories of installed or uninstalled fix packs and
  interim fixes. It reads Installation Manager's history.xml and
  then calls SimpleXML parser to parse it to a DOM tree in JVM
  memory. This requires a lot of memory if the history.xml is
  very large. At default, the historyInfo command sets the
  maximum JVM memory to 512M. The command will fail If the
  parsed history.xml DOM tree takes memory more than 512M.
  

Problem conclusion

• The fix was to replace the SimpleXML parser with the Java StAX
  Parser. It runs faster with very low memory.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.10.  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