PH60295: NULLPOINTEREXCEPTION OCCURS DURING THE JAVA CORE ACTION IN THE DIAGNOSTIC PLAN, WHEN -XDUMP:LOCATION IS USED.

APAR status

• Closed as program error.

Error description

• If the location of the java core files is set using the -
  Xdump:location, the Diagnostic Plan fails after the first java
  core is generated.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: NullPointerException occurs during the  *
  *                      Java core action in the Diagnostic      *
  *                      Plan,                                   *
  *                      when the -Xdump:directory option is     *
  *                      used.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the -Xdump:directory option is set, a NullPointerException
  occurs, during the Java core action in the Diagnostic Plan.
  DumpJavaCoreA I TRAS1107I: JAVACORE action completed. The
  generated java core file is at <null>.
  TRAS1130W: The diagnostic plan has encountered an error and is
  cancelled. java.lang.NullPointerException
  at
  com.ibm.ws.logging.diagplan.ActionsController.executeAction(Acti
  o
  nsController.java:200)
  at
  com.ibm.ws.logging.diagplan.DiagPlanManager$2.run(DiagPlanManage
  r
  .java:114)
  ...
  StackTrace: java.lang.NullPointerException
  at
  com.ibm.ws.logging.diagplan.ActionSummaryHandler.formatEventEntr
  y
  (ActionSummaryHandler.java:188)
  at
  com.ibm.ws.logging.diagplan.ActionSummaryHandler.logActionSummar
  y
  (ActionSummaryHandler.java:121)
  at
  com.ibm.ws.logging.diagplan.ActionsController.logSummary(Actions
  C
  ontroller.java:230)
  at
  com.ibm.ws.logging.diagplan.actions.DiagnosticActionImpl.stop(Di
  a
  gnosticActionImpl.java:69)
  at
  com.ibm.ws.logging.diagplan.actions.DumpJavaCoreAction.execute(D
  u
  mpJavaCoreAction.java:142)
  at
  com.ibm.ws.logging.diagplan.ActionsController.executeAction(Acti
  o
  nsController.java:192)
  at
  com.ibm.ws.logging.diagplan.DiagPlanManager$2.run(DiagPlanManage
  r
  .java:114)
  

Problem conclusion

• The code was fixed, to resolve this issue.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.27 and 9.0.5.23. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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