PI16935: JAVAX.NAMING.NAMENOTFOUNDEXCEPTION FOR EJB3.1 EJB IN SERVANT REGIONS STARTED AFTER THE FIRST SERVANT REGION COMES UP.

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

• Once the application is deployed and started, it is able to
  complete JNDI lookups for TestEJB successfully in the first
  servant that is started, but in the rest of the servants, the
  application encounters this exception
  javax.naming.NameNotFoundException:
  Name "AccessLogBean" not found in context "java:module".
  at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal
  (NameSpace.java:1228)
  at com.ibm.ws.naming.ipbase.NameSpace.lookup
  (NameSpace.java:1141)
  ...
  

Local fix

• change EJB lookup to not use java: namespace lookups
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of Enterprise Java Beans (EJBs) on    *
  *                  servers with multiple servants              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The java:module context is only         *
  *                      populated in the first servant region.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The EJB container only binds EJBs in the first servant
  region that starts for performance.  For most contexts, this
  is correct because the contexts are stored in the control
  region and are shared amongst all servant regions, but it is
  not correct for the java:module context, which is local-only.
  

Problem conclusion

• The EJB container has been corrected to bind EJBs to the
  java:module context in all servant regions.
  
  APAR PI16935 is currently targeted for inclusion in Fix Pack
  8.0.0.10 of WebSphere Application Server.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

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 FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R800 PSY

     UP