PM38438: DURING SERVER STARTUP, A NULLPOINTEREXCEPTION OCCURS IN COMMONPLUGIN$IMPLEMENTATION.LOADCLASS

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• A NullPointerException occurs during the startup of an
  application. The stack is:
  
  java.lang.NullPointerException
  at org.eclipse.emf.common.
      CommonPlugin$Implementation.loadClass(CommonPlugin.java:198)
  at org.eclipse.emf.common.
      CommonPlugin.loadClass(CommonPlugin.java:98)
  at org.eclipse.emf.ecore.xmi.util.
      DefaultEcoreBuilder.<clinit>(DefaultEcoreBuilder.java:54)
  at java.lang.J9VMInternals.initializeImpl(Native Method)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:205)
  at org.eclipse.emf.ecore.xmi.impl.
      XMLHandler.createEcoreBuilder(XMLHandler.java:2822)
  at org.eclipse.emf.ecore.xmi.impl.
      XMLHandler.<init>(XMLHandler.java:397)
  at org.eclipse.emf.ecore.xmi.impl.
      SAXXMLHandler.<init>(SAXXMLHandler.java:44)
  at org.eclipse.emf.ecore.xmi.impl.
      XMLLoadImpl.makeDefaultHandler(XMLLoadImpl.java:310)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application startup generates           *
  *                      NullPointerException from               *
  *                      class CommonPlugin and method           *
  *                      loadClass in system error log files.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A NullPointerException can occur during the startup of an
  application.  The exception appears in the application
  server trace log files and in the application system error log
  files.  For example:
  
  java.lang.NullPointerException
  at org.eclipse.emf.common.CommonPlugin$Implementation.
  loadClass(CommonPlugin.java:198)
  at org.eclipse.emf.common.CommonPlugin.
  loadClass(CommonPlugin.java:98)
  at org.eclipse.emf.ecore.xmi.util.DefaultEcoreBuilder.
  <clinit>(DefaultEcoreBuilder.java:54)
  at java.lang.J9VMInternals.initializeImpl(Native Method)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:205)
  at org.eclipse.emf.ecore.xmi.impl.XMLHandler.
  createEcoreBuilder(XMLHandler.java:2822)
  at org.eclipse.emf.ecore.xmi.impl.XMLHandler.
  <init>(XMLHandler.java:397)
  at org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.
  <init>(SAXXMLHandle r.java:44)
  at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.
  makeDefaultHandler(XMLLoadImpl.java:310)
  
  Processing continues following the exception, however, memory
  usage increases by up to 5% and additional processing is
  triggered for the application which is being started.
  
  The problem is specific to applications which have JavaEE5
  enabled modules.
  

Problem conclusion

• The problem occurs because of a faulty code dependency in the
  code used to load the XML file "ibm-metadata.xml".  The XML file
  "ibm-metadata.xml" is a new IBM generated file which is used to
  store annotations derived module metadata.  The faulty
  dependency causes an attempt to load a class which is not
  necessary for the XML load.
  
  The problem was resolved by removing the unnecessary code
  dependency from the code used to load "ibm-metadata.xml".
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP