PK75899: RESTART OF EJB WITH MULTIPLE SERVANTS WSVR0046E: UNABLE TO BIND ORG.OMG.COSNAMING.NAMINGCONTEXTPACKAGE.ALREADYBOUND

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In a WebSphere for z/OS server that is running with a multiple
  Servant region configuration, restarting an application
  containing EJBs causes the following WSVR0046E errors to surface
  in some Servant regions:
  .
   Trace: 2008/07/14 20:36:17.910 01 t=8CB5B0 c=UNK key=P8
  (13007002)
     ThreadId: 0000003f
     FunctionName: com.ibm.ws.runtime.component.EJBContainerImpl
     SourceId: com.ibm.ws.runtime.component.EJBContainerImpl
     Category: SEVERE
     ExtendedMessage: BBOO0220E: WSVR0046E: Unable to bind,
  ejb/InteropV61EJBHome: ejb/InteropV61EJBHome. Original exception
  :
  org.omg.
   CosNaming.NamingContextPackage.AlreadyBound:
  IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0
   Trace: 2008/07/14 20:36:17.911 01 t=8CB5B0 c=UNK key=P8
  (0000000A)
     Description: Log Java Message
     Message: BBOO0220E: WSVR0046E: Unable to bind,
  ejb/InteropV61EJBHome:
  ejb/InteropV61EJBHome. Original exception : org.omg.CosNamin
   g.NamingContextPackage.AlreadyBound:
  IDL:omg.org/CosNaming/NamingContext/AlreadyBound:1.0
  com.ibm.ws.runtime.component.EJBContainerI
   mpl com.ibm.ws.runtime.component.EJBContainerImpl
  .
  In the above example, the relevant EJB had a JNDI name of
  ejb/InteropV61EJBHome.
  .
  When reproducing the problem we found that the application
  continued to work ok even after the WSVR0046E errors.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server for z/OS    *
  *                 versions 7.0 users of EJBs and multiple      *
  *                 servant regions.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The WSVR0046E message will be printed   *
  *                      while restarting applications from      *
  *                      all servant regions except the first.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The EJB container relies on the application manager to
  determine whether remote EJB homes for an application need to
  be bound or unbound in a particular servant.  The application
  manager has no mechanism for coordinating amongst multiple
  servants during a dynamic application stop or start, so the
  EJB container makes an attempt to bind remote EJB homes in all
  servants, which results in a WSVR0046E message with a
  NameAlreadyBoundException.
  

Problem conclusion

• A mechanism was added to the application manager to coordinate
  binds and unbinds amongst multiple servants during dynamic
  application stop or start.
  
  APAR PK75899 is currently targeted for inclusion in Service
  Level (Fix Pack) 7.0.0.1 of WebSphere Application Server V7.0
  for z/OS.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK69743

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UK41764

     UP08/12/05 P F812

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.