PM72770: CALLING CONTEXT.REBIND(NAME, OBJ) DOES NOT PERFORM THE EXPECTED BIND

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• Error Description:
  
  NameNotFoundException thrown when calling context.rebind(name,
  obj) when an initial binding has not been performed.  The
  expected behavior is that a bind would occur when calling
  rebind as long as all intermediate contexts and the target
  context already exist.
  
  Exception Stack  :
  
  12/09/07 13:30:49:515 JST 00000023 SystemErr
  javax.naming.NameNotFoundException: name1
  12/09/07 13:30:49:515 JST 00000023 SystemErr
  at
  com.ibm.ws.jndi.internal.ContextNode.lookup(ContextNode.java
  12/09/07 13:30:49:515 JST 00000023 SystemErr
   at
  com.ibm.ws.jndi.internal.WSContext.unbind(WSContext.java:449
  12/09/07 13:30:49:515 JST 00000023 SystemErr
  at
  com.ibm.ws.jndi.internal.WSContext.rebind(WSContext.java:351
  12/09/07 13:30:49:515 JST 00000023 SystemErr
  at
  com.ibm.ws.jndi.internal.WSContext.rebind(WSContext.java:346
  12/09/07 13:30:49:515 JST 00000023 SystemErr
  
  The problem appears only on WebSphere Application Server Liberty
  Profile
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile using JNDI.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Calling context.rebind(name, obj) can   *
  *                      result in a NameNotFoundException.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an initial binding has not been performed, calling
  context.rebind(name, obj) results in a NameNotFoundException.
  

Problem conclusion

• Calling context.rebind(name, obj) no longer requires the
  object to have been previously bound, and a binding will be
  performed regardless.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.0.2. 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP