PK27020: BINDING MULTIPLE HOMES FROM MULTIPLE APPLICATIONS SIMULTANEOULSLY MAY RESULT IN UNEXPECTED NAMEALREADYBOUNDEXC.'S

6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for HP-UX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for AIX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Windows
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Linux
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for i5/OS
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Solaris

APAR status

• Closed as program error.

Error description

• Binding Multiple homes from multiple applications simultaneously
  may result in "unexpected" NameAlreadyBoundExceptions to show u
  p in the log.   NameAlreadyBoundExceptions common and normally d
  o not indicate that anything is wrong.  In this case however the
   NameAlreadyBoundException is occurring and a local home is not
  being bound in naming.   This will cause a lookup of this home t
  o fail later.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 version 6 Enterprise java beans.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: During simultaneous starting of         *
  *                      applications, homes or subcontexts are  *
  *                      failing to bind into jndi with          *
  *                      javax.naming.NameAlreadyBoundException  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When starting several applications simultaneously
  javax.naming.NameAlreadyBoundException may occur and prevent
  homes or subcontext from being bound into jndi.   ***NOTE***
  javax.naming.NameAlreadyBoundException is an exception that
  can occur quite often with absolutely no problem, and, by
  itself, is not an indication of any failure.  The key to this
  failure is that homes or subcontexts are not being bound into
  jndi. ***
  

Problem conclusion

• The code in jndi helper was found to not be "thread-safe".
  Altering the jndi helper code to be thread-safe was deemed to
  be to risky and therefore the EJBContainer code was changed to
  synchronize certain calls to the jndiHelper code which binds
  the subcontexts and home.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpacks 6.0.2.13 and 6.1.0.1.
  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:

Modules/Macros

• EJBCNTR
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP