PH34673: APPLICATION START/STOP ISSUES IN WEBSPHERE APPLICATION SERVER ND V9.0.5.5.X

APAR status

• Closed as program error.

Error description

• An EJB Application is installed and running on WebSphere ND
  9.0.5.5.x. When an attempt is made to stop the application from
  AdminConsole, the following errors are displayed:
  The operation on XXX application did not complete in the
  expected amount of time. It might have completed successfully.
  Check the logs for details. Application XXX did not stop
  successfully on all of the servers in the cluster. Check the log
  for details
  
  However, SystemOut.log shows that the application is stopped:
  WSVR0220I: Application stopped: XXX.war
  WSVR0193I: Composition unit WebSphere:XXX.war in BLA
  WebSphere:blaname=XXX.war stopped.
  
  During the stop, the following ffdc is produced:
  FFDC Exception:com.ibm.ws.cdi.CDIRuntimeException
  SourceId:com.ibm.ws.runtime.component.DeployedApplicationImpl
  ProbeId:556
  com.ibm.ws.cdi.CDIRuntimeException:
  com.ibm.ws.cdi.CDIRuntimeException:
  java.lang.IllegalStateException: Unable to find BeanManager.
  Please ensure that you configured the CDI implementation of your
  choice properly.
   at
  com.ibm.ws.cdi.classic.CDIRuntimeImpl.stop(CDIRuntimeImpl.java:4
  69)
   ..
  Caused by: java.lang.IllegalStateException: Unable to find
  BeanManager. Please ensure that you configured the CDI
  implementation of your choice properly.
   at
  org.apache.deltaspike.core.api.provider.BeanManagerProvider.getB
  eanManager(BeanManagerProvider.java:256)
  ...
   at
  org.jboss.weld.context.AbstractContext.destroy(AbstractContext.j
  ava:153)
   ..
  When attempting to start the application afterwards ,the
  following errors are displayed in the AdminConsole:
  Application XXX failed to start. Check the logs for server xxx
  for details.
  An error occurred while starting XXX. Check the logs for server
  xxx for more details.
  Application XXX did not start successfully on all of the server
  in cluster xxx. Check log for details.
  
  Following errors are logged in the SystemOut.log:
  WSVR0193I: Composition unit WebSphere:XXX.war in BLA
  WebSphere:blaname=XXX.war stopped.
  CWWJP0019W: The XXX.war application has already started.
  WSVR0101W: An error occurred starting, XXX.war
  WSVR0217I: Stopping application: XXX.war
  
  The following FFDC is produced:
  FFDC
  Exception:com.ibm.ws.naming.distcos.NameSpaceConstructionExcepti
  on
  SourceId:com.ibm.ws.naming.bootstrap.NameServerImpl.starting_app
  ProbeId:1185 Reporter:java.lang.Class@5c3e9f15
  com.ibm.ws.naming.distcos.NameSpaceConstructionException: Object
  bound with the name "XXX.war" under the applications root
  context already exists.
   at
  com.ibm.ws.naming.distcos.NameSpaceBuilder.createJavaAppNameSpac
  e(NameSpaceBuilder.java:645)
   at
  com.ibm.ws.naming.bootstrap.NameServerImpl.starting_app(NameServ
  erImpl.java:1183)
   at
  com.ibm.ws.naming.bootstrap.NameServerImpl$Listener.handleAppSta
  rtingEvent(NameServerImpl.java:1496)
   at
  com.ibm.ws.naming.bootstrap.DeployedObjectListenerImpl.handleSta
  rtingEvent(DeployedObjectListenerImpl.java:204)
   ....
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: IllegalStateException: Unable to find   *
  *                      BeanManager during application stop     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During application startup and shutdown CDI may not be able to
  find the correct bean manager from the currently active
  thread. Thus an additional thread local was added, it was set
  when an application was starting but not when an application
  was stopping.
  

Problem conclusion

• The threadlocal is now set during application shutdown.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.5.0.9. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

• R900 PSY

     UP