PI49978: If CDI 1.2 is enabled then a BeanManager could be returned when resolving any JNDI value.

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• If a value is programmatically bound into JNDI using
  InitialContext.bind() then when the variable is resolved
  using InitialContext.lookup(), it will always return the
  current CDI BeanManager instead of the real value. This only
  occurs if CDI 1.2 is enabled and the value is
  programmatically bound. It will not occur if the value is
  specified as a jndiEntry in the server.xml.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using CDI 1.2 and JNDI               *
  ****************************************************************
  * PROBLEM DESCRIPTION: If CDI 1.2 is enabled then a            *
  *                      BeanManager could be returned when      *
  *                      resolving any JNDI value.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a value is programmatically bound into JNDI using
  InitialContext.bind() then when the variable is resolved using
  InitialContext.lookup(), it will always return the current CDI
  BeanManager instead of the real value. This only occurs if CDI
  1.2 is enabled and the value is programmatically bound. It will
  not occur if the value is specified as a jndiEntry in the
  server.xml.
  

Problem conclusion

• We have fixed the CDI BeanManager ObjectFactory to only return a
  BeanManager when the JNDI object being resolved is a Reference
  and not, for example, just a String.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.8.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Use a jndiEntry in the server.xml to configure JNDI values
  rather than adding them via the InitialContext.
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP