PM96235: Unhandled exception during the initialization of the ServletContainerInitializer

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
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

• Unhandled exception during the initialization of the
  ServletContainerInitializer
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Liberty    *
  *                  Core version 8.5 users of                   *
  *                  ServletContainerInitializer                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: A java.lang.NoClassDefFoundError        *
  *                      exception is not caught and handled     *
  *                      accordingly.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A request to an application, which is using the
  ServletContainerInitializer feature, might fail with a
  java.lang.NoClassDefFoundError exception.  An example of the
  exception stack:
  Exception = java.lang.NoClassDefFoundError
  Source = com.ibm.ws.webcontainer.osgi.VirtualHost
  probeid = startWebApp
  Stack Dump = java.lang.NoClassDefFoundError:
  org/example/ExampleClass
  at
  org.example.ExampleClass.<clinit>(ExampleClass.java:46)
  at java.lang.Class.forName0(Native Method)
  at java.lang.Class.forName(Class.java:247)
  at
  com.ibm.ws.webcontainer.osgi.webapp.WebApp.addClassToHandlesType
  sStartupSet(WebApp.java:1097)
  at
  com.ibm.ws.webcontainer.osgi.webapp.WebApp.scanForHandlesTypesCl
  asses(WebApp.java:963)
  at
  com.ibm.ws.webcontainer.webapp.WebApp.initializeServletContainer
  Initializers(WebApp.java:2304)
  at
  com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:950
  )
  at
  com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:603
  8)
  According to the JavaServlet specification the container might
  not know whether the missing class will prevent the
  application from working correctly, it must log the exceptions
  and ignore them.
  

Problem conclusion

• The WebContainer code was modified to log the missing class
  exception and allow the request to continue.
  
  The fix for this APAR is currently targeted for inclusion in
  Liberty Core fix pack 8.5.5.2.
  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP