IBM Support

PK69778: DYNAMIC CACHE INSTANCE FAILED TO INITIALIZE WITH NAMEALREADYBOUNDEXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting the application server with multiple applications
    using the same cache instance, the below exception occurs
    randonly during startup:
    
    [7/24/08 13:29:34:737 EDT] 00000035 CacheServiceI E   DYNA1003E:
    WebSphere Dynamic Cache instance named
    directory/cache/MyCache can not be initialized
    because of error javax.naming.NameAlreadyBoundException
     at
    com.ibm.ws.naming.jndicos.CNContextImpl.doCreateSubcontext(CNCon
    textImpl.java:2841)
     at
    com.ibm.ws.naming.jndicos.CNContextImpl.createSubcontext(CNConte
    xtImpl.java:967)
     at
    com.ibm.websphere.naming.JndiHelper.createSubcontexts(JndiHelper
    .java:346)
     at
    com.ibm.websphere.naming.JndiHelper.createSubcontexts(JndiHelper
    .java:342)
     at
    com.ibm.websphere.naming.JndiHelper.createSubcontextsDriver(Jndi
    Helper.java:288)
     at
    com.ibm.websphere.naming.JndiHelper.recursiveBind(JndiHelper.jav
    a:575)
     at
    com.ibm.websphere.naming.JndiHelper.recursiveBind(JndiHelper.jav
    a:420)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  with multiple applications using the same   *
    *                  cache instance.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NameAlreadyBoundException can occur   *
    *                      during server start up when multiple    *
    *                      applications are using the same cache.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When multiple applications using the same cache instance are
    started simultaneously the bindings to JNDI may collide and
    cause the NameAlreadyBoundException to be logged.
    The exception is expected, however, if an application
    using the same cache instance has already bound to JNDI.  In
    this case the exception should be ignored.
    

Problem conclusion

  • The method performing the binding to JNDI has been
    synchronized to prevent multiple threads from simultaneously
    performing the bind.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.0.2.33 and 6.1.0.23.  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 number

    PK69778

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-07-29

  • Closed date

    2008-11-12

  • Last modified date

    2008-11-12

  • 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

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021