PI13720: APPLICATION SERVER JVM CAN NOT BE STARTED AFTER MAKING AN UPDATE TO THE DYNAMIC SERVER TEMPLATE

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• Application server jvm can not be started after making an
  update to the dynamic server template
  

Local fix

• Customer workaround provided.  Switching the JVM to use HPEL
  logging allows them to start the JVM
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The server fails to start with an       *
  *                      IllegalStateException at                *
  *                      com.ibm.ws.config.ModelMgr.initializeMo *
  *                      dels(ModelMgr.java:355)                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The java.lang.IllegalStateException is caused by a nested
  NullPointerException with the stack:
  java.lang.NullPointerException
  at
  org.eclipse.jem.java.internal.impl.JavaRefPackageImpl.initialize
  PackageContents(JavaRefPackageImpl.java:819)
  at
  org.eclipse.jem.java.internal.impl.JavaRefPackageImpl.initGen(Ja
  vaRefPackageImpl.java:232)
  at
  org.eclipse.jem.java.internal.impl.JavaRefPackageImpl.init(JavaR
  efPackageImpl.java:211)
  at
  org.eclipse.jem.java.JavaRefPackage.<clinit>(JavaRefPackage.java
  :1564)
  at java.lang.J9VMInternals.initializeImpl(Native Method)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:236)
  ... 47 more
  The root NullPointerException is caused by
  EPackageRegistryImpl.get returning null for the Ecore package
  with the key http://www.eclipse.org/emf/2002/Ecore.
  This happens because the package for the key
  "http://www.eclipse.org/emf/2002/Ecore" was registered under
  one Classloader and retrieved using another. The difference is
  the ContextClassloader (CCL) has changed between the
  registration and retrieval.
  

Problem conclusion

• The initialization code was changed to explicitly force the
  Ecore model initialization to run at a specific point, when it
  is known that the correct context classloader is in use.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3.  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