PK47714: JNDI LOOKUPS IN THE COMPONENT NAMESPACE (JAVA:COMP/ENV) OF WEB MODULES FAIL AFTER UPGRADE TO VERSION 6.0.2.19/PK34085

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• After an upgrade from WebSphere Application Server V6.0.2.15 to
  V6.0.2.19 on AIX V5.3, JNDI lookups in the component
  namespace (java:comp/env) of web modules do not work any more.
  There are also problems with references to WebSphere MQ
  connection factories.  Direct JNDI lookups (not in the
  java:comp/env namespace) of the queue connection factories work
  fine.  Component namespace lookups work also in ejb modules.
  Component namespace lookups work in web modules with a
  servlet spec 2.4 aplication.
  PROBLEM SUMMARY:
  JNDI LOOKUPS IN THE COMPONENT NAMESPACE (JAVA:COMP/ENV) OF WEB
  MODULES FAIL AFTER UPGRADE TO VERSION 6.0.2.19
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server versions    *
  *                 6.0.2 and 6.1 users of filters who rely on   *
  *                 data in the WebComponentMetaData object      *
  *                 after PK34085.                               *
  *                 For example users who do a JNDI lookup       *
  *                 as part of a request after a filter is       *
  *                 called.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: JNDI lookups in the component           *
  *                      namespace (java:comp/env) of web        *
  *                      modules result in a                     *
  *                      javax.naming.ConfigurationException     *
  *                      after PK34085.                          *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JNDI lookups in the component namespace (JAVA:COMP/ENV) of
  web modules do not work after upgrade to version 6.0.2.19
  
  In PK34085 the Webcontainer was changed to create a copy
  of a WebComponentMetaData object for use when calling filters.
  However the object was created before all data used to create
  it was fully initialized. As a result data was missing which,
  for example, JNDI lookups are dependent upon.
  
  As a result of this missing data a JNDI lookup may fail with
  the following messages and exception:
  
  [<date + time>] 00000039 javaURLContex W   NMSV0308W:
  javaURLContextFactory cannot create a javaURLContext object
  because there is no java URL name space currently
  accessible from the executing thread.
  
  [<date + time>] 00000039 javaURLContex W   NMSV0308W:
  javaURLContextFactory cannot create a javaURLContext object
  because there is no java URL name space currently accessible
  from the executing thread.
  
  [<date + time>] 00000039 Helpers       W   NMSV0610I: A
  NamingException is being thrown from a javax.naming.Context
  implementation. Details follow:
  
  Exception stack trace: javax.naming.ConfigurationException:
  
  NamingManager.getURLContext cannot find the factory for
  this scheme: java
          at
  com.ibm.ws.naming.jndicos.CNContextImpl.checkForUrlContext
  (CNContextImpl.java:3114)
          at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt
  (CNContextImpl.java:1407)
          at com.ibm.ws.naming.jndicos.CNContextImpl.lookup
  (CNContextImpl.java:1290)
          at com.ibm.ws.naming.util.WsnInitCtx.lookup
  (WsnInitCtx.java:145)
          at javax.naming.InitialContext.lookup
  (InitialContext.java:361)
  etc.
  

Problem conclusion

• The webcontainer has been updated to ensure that fully
  initialized objects are used when creating the
  WebComponentMetaData object.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpacks 6.0.2.23 and 6.1.0.11.
  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:

  PK49574

Modules/Macros

• ENGINE
  

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