PM54357: EJBS WITH NAMES CONTAINING A SLASH CANNOT BE STARTED

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
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

• For an ejb-name test/TestBean, the following error occurs:
  
  Caused by: javax.naming.NameNotFoundException: name =
  test/TestBean!test.TestIntf: first name component of test
  is not found.
  Original exception :
  org.omg.CosNaming.NamingContextPackage.NotFound:
  IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
  at com.ibm.ws.naming.jbatch.CommonBatchModeCNContextImpl.
  processException(CommonBatchModeCNContextImpl.java:456)
  at com.ibm.ws.naming.jbatch.CommonBatchModeCNContextImpl.
  lookupPostProcess(CommonBatchModeCNContextImpl.java:1032)
  at com.ibm.ws.naming.jbatch.CommonBatchModeCNContextImpl.
  lookupPostProcess(CommonBatchModeCNContextImpl.java:1014)
  at com.ibm.ws.naming.jbatch.CommonBatchModeCNContextImpl.
  unbindPostProcess(CommonBatchModeCNContextImpl.java:724)
  at com.ibm.ws.naming.jbatch.CommonBatchModeCNContextImpl.
  executeBatchedOperations(CommonBatchModeCNContextImpl.java:1645)
  at om.ibm.ws.naming.jbatch.javaCNBatchContextImpl.
  executeBatchedOperations(javaCNBatchContextImpl.java:278)
  at com.ibm.ws.ejbcontainer.runtime.AbstractEJBRuntime.
  executeBatchedOperation(AbstractEJBRuntime.java:1416)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V8.0 users *
  *                  of Enterprise Java Beans (EJBs)             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Starting a module containing an EJB     *
  *                      with a name containing a forward        *
  *                      slash will fail.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an EJB module is started, the EJB container must bind to
  the java:global namespace using the format
  java:global/APP/MOD/BEAN!INTERFACE.  If the bean name contains
  a forward slash, the Java Name and Directy Interface (JNDI)
  bind operation will fail because forward slash is the
  delimiter.  EJB names containing forward slashes are not
  permitted by the EJB specification.
  

Problem conclusion

• The EJB container is updated to avoid binding to java:global
  if the EJB name contains a forward slash.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.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

• R800 PSY

     UP