PK61958: NULLPOINTEREXCEPTION WHILE CREATING FFDC

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• The following exception may be seen when trying to create an
  FFDC.  The failure to create the FFDC may hide useful
  information in identifying the original problem that triggered
  the FFDC.
  
  The NullPointerException is:
  Caused by: java.lang.NullPointerException
  at com.ibm.ws.sib.processor.impl.store.items.MessageItem.
     toString(MessageItem.java:1359)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
     toFFDCStringSingleObject(SibDiagnosticModule.java:366)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
     toFFDCString(SibDiagnosticModule.java:334)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
     ffdcDumpDefault(SibDiagnosticModule.java:292)
  ... 28 more
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the default messaging provider in   *
  *                 WebSphere Application Server v6.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: If an error occurs when two messaging   *
  *                      engines are communicating with each     *
  *                      other it is possible the related FFDC   *
  *                      will not be written.  An                *
  *                      InvocationTargetException may be seen   *
  *                      when writing the FFDC, caused by a      *
  *                      NullPointerException.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an error occurs when two messaging engines are
  communicating an FFDC should be written detailing the error.
  In some circumstances the writing of the FFDC may fail with an
  InvocationTargetException caused by an earlier
  NullPointerException.  This prevents useful information about
  the original error being logged.
  
  For example
  
  java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(
     NativeMethodAccessorImpl.java:79)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
     DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:618)
  at com.ibm.ws.ffdc.DiagnosticModule.getDataForDirective(
     DiagnosticModule.java:316)
  ...
  
  Caused by: java.lang.NullPointerException
  at com.ibm.ws.sib.processor.impl.store.items.MessageItem.
     toString(MessageItem.java:1359)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
     toFFDCStringSingleObject(SibDiagnosticModule.java:366)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
     toFFDCString(SibDiagnosticModule.java:334)
  at com.ibm.ws.sib.utils.ffdc.SibDiagnosticModule.
  ffdcDumpDefault(SibDiagnosticModule.java:292)
  ... 28 more
  

Problem conclusion

• This APAR fixes the NullPointerException allowing the FFDC to
  be written.
  

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

  PLAT MSG COM

• Fixed component ID

  620600101

Applicable component levels

• R200 PSY

     UP