PI27557: NULLPOINTEREXCEPTION WHEN THERE IS AN ACTIVE REQUEST AND THE SERVER IS SHUTTING DOWN

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

• An example of this exception is:
  java.lang.NullPointerException
  > at
  com.ibm.ws.webcontainer.webapp.WebApp.getErrorPageDispatcher(Web
  App.java:4185)
  > at
  com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:3890
  )
  > at
  com.ibm.ws.webcontainer.webapp.WebApp.handleException(WebApp.jav
  a:4548)
  > at
  com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:
  4529)
  > at
  com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.handleRequest(
  DynamicVirtualHost.java:282)
  > at
  com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
  java:954)
  > at
  com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVir
  tualHost.java:252)
  > at
  com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$T
  askWrapper.run(HttpDispatcherLink.java:590)
  > at
  com.ibm.ws.threading.internal.Worker.executeWork(Worker.java:439
  )
  > at com.ibm.ws.threading.internal.Worker.run(Worker.java:421)
  > at java.lang.Thread.run(Thread.java:770)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile version 8.5.5        *
  ****************************************************************
  * PROBLEM DESCRIPTION: A java.lang.NullPointerException is     *
  *                      thrown when there is an active request  *
  *                      and the server is shutting down.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A NullPointerException is thrown from
  org.eclipse.osgi.internal.module.ResolverImpl.resolveDynamicImpo
  rt due to the fact that the server has been issued a shutdown
  instruction while still handling an active request.
  An example of this exception is:
  java.lang.NullPointerException
  >	at
  com.ibm.ws.webcontainer.webapp.WebApp.getErrorPageDispatcher(Web
  App.java:4185)
  >	at
  com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:3890
  )
  >	at
  com.ibm.ws.webcontainer.webapp.WebApp.handleException(WebApp.jav
  a:4548)
  >	at
  com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:
  4529)
  >	at
  com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.handleRequest(
  DynamicVirtualHost.java:282)
  >	at
  com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
  java:954)
  >	at
  com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVir
  tualHost.java:252)
  >	at
  com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$T
  askWrapper.run(HttpDispatcherLink.java:590)
  >	at
  com.ibm.ws.threading.internal.Worker.executeWork(Worker.java:439
  )
  >	at com.ibm.ws.threading.internal.Worker.run(Worker.java:421)
  >	at java.lang.Thread.run(Thread.java:770)
  

Problem conclusion

• The Web Container code was modified so that a 404 Context Root
  Not Found response is returned when the Web Container is not
  able to finish processing a request due to application removal.
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.4.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• NA
  

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