PI94494: LOOKUP FOR THE JAVA:APP RESULTS IN CONFIGURATIONEXCEPTION IF THE LOOKUP HAPPENS DURING THE STARTUP OF THE APP.

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• If we try to lookup the env-entry in java:app namespace during
  the application startup, it results in the following exception.
  ---------------------------------
  javax.naming.ConfigurationException: A JNDI operation on a
  "java:" name cannot be completed because the server runtime is
  not able to associate the operation's thread with any J2EE
  application component.  This condition can occur when the JNDI
  client using the "java:" name is not  executed on the thread
  of a server application request.
  ---------------------------------
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: JNDI lookups do not work during CDI     *
  *                      bootstrapping                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CDI bootstrapping can trigger application code with observer
  methods, however this took place before the JNDI namespaces
  were initilized
  

Problem conclusion

• The order of events during application startup has been
  reworked. Due to architectural limitations only the java:app
  namespace should be used inside CDI observers that activate
  during application startup
  
  The fix for this APAR is currently targeted for inclusion in
  fixpacks 9.0.0.8 and 18.0.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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP