PI34203: EXCEPTIONS IN WAS WHEN GETTING IBM.WORKLIGHT.ADMIN PROPERTIES

IBM Worklight Interim Fix README for 6.2.0.1

APAR status

• Closed as program error.

Error description

• Exceptions such as:
  
  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.  Make sure that a J2EE application
  does not execute JNDI operations on "java:" names within static
  code blocks or in threads created by that J2EE application.
  Such code does not necessarily run on the thread of a server
  application request and therefore is not supported by JNDI
  operations on "java:" names. [Root exception is
  javax.naming.NameNotFoundException: Name
  "comp/env/ibm.worklight.admin.actions.commitRejectTimeout" not
  found in context "java:".]
  
  may appear in the server logs when running on the WebSphere
  Application Server and trying to retrieve the properties
  ibm.worklight.admin.actions.commitRejectTimeout,
  ibm.worklight.admin.actions.prepareTimeout or
  ibm.worklight.admin.lockTimeoutInMillis.
  

Local fix

• These messages may be safely ignored unless you try to set one
  of the JNDI property names.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the Worklight console in a WebSphere            *
  * Application Server environment                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Exceptions are emitted in the WebSphere Application Server   *
  * ffdc files concerning JNDI lookup like :                     *
  *                                                              *
  * 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.  Make sure that  *
  * a J2EE application does not execute JNDI operations on       *
  * "java:" names within static code blocks or in threads        *
  * created by that J2EE application.  Such code does not        *
  * necessarily run on the thread of a server application        *
  * request and therefore is not supported by JNDI operations on *
  * "java:" names. [Root exception is                            *
  * javax.naming.NameNotFoundException: Name                     *
  * "comp/env/ibm.worklight.admin.actions.commitRejectTimeout"   *
  * not found in context "java:".]                               *
  *                                                              *
  * This concerns the following JNDI Properties:                 *
  * ibm.worklight.admin.actions.prepareTimeout,                  *
  * ibm.worklight.admin.actions.commitRejectTimeout and          *
  * ibm.worklight.admin.lockTimeoutInMillis                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• No more exceptions are emitted for these JNDI properties.
  

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

  WL/MFPF ENTERPR

• Fixed component ID

  5725I4300

Applicable component levels

• R620 PSY

     UP

• R630 PSY

     UP