PI51010: Liberty core dumps when -Xhealthcenter:level=inprocess jvm optio n is used with health center agent version 3.0.5 or above

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

• Health manager feature internally uses health center agent
  to retrieve JVM monitoring and diagnostic information.
  
  Health center agent version 3.0.5 or above supports a
  programmatic way of connecting to the health center agent.
  The code uses this feature to automatically load and connect
  to the health center agent when the health management
  feature is enabled.
  
  When using the -Xhealthcenter:level=inprocess jvm option
  with health center agent 3.0.5 or above, the JVM crashes.
  This crash is caused because the health center agent gets
  loaded twice; once in the code and once from the JVM option.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile - Debug/Tracing      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Liberty profile core dumps when -       *
  *                      Xhealthcenter:level=inprocess jvm       *
  *                      option is used with health center agent *
  *                      version 3.0.5 or above                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The healthAnalyzer-1.0 feature internally uses the health center
  agent to retrieve JVM monitoring and diagnostic information.
  Health center agent version 3.0.5 or above supports a
  programmatic way of connecting to the health center agent. The
  code uses this feature to automatically load and connect to the
  health center agent when the health management feature is
  enabled. When used with the -Xhealthcenter:level=inprocess jvm
  option, health center agent 3.0.5 or above causes the JVM to
  crash. This crash is caused because the health center agent
  getting loaded twice, once in the code and once from the JVM
  option.
  

Problem conclusion

• The code was modified to check if the -
  Xhealthcenter:level=inprocess flag is enabled for health center
  agent version 3.0.5 or greater, in which case the code doesn't
  attempt to load the agent programmatically.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.8.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Remove the -Xhealthcenter:level=inprocess option, as health
  center agent 3.0.5 or above will automatically get loaded by the
  code.
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP