PM79980: JAVAX.NAMING.CONFIGURATIONEXCEPTION WHILE TRYING TO INVOKE REMOTEMETASERVICE WITH COMMAND SMIU.CHECKCREDENTIALS.

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• 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.
  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/ejb" not
  found in
  context "java:".]{caused by: javax.naming.NameNotFoundException:
  Name
  "comp/env/ejb" not found in context "java:".}
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty profile.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: A resource JNDI lookup fails from a     *
  *                      filter mapped to the                    *
  *                      /j_security_check URI.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The server has not invoked the correct namespace on the thread
  associated with the web application resulting in a
  javax.naming.ConfigurationException.
  

Problem conclusion

• The webcontainer code has been fixed and the resource JNDI
  lookup works from a filter mapped to the /j_security_check
  URI.
  
  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:

  PM78898

• 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