PI85892:classcastexceptions while doing a naming lookup for beanmanger

Download Description

PI85892 resolves the following problem:

ERROR DESCRIPTION:
ClassCastExceptions while doing a naming lookup for beanManger.

###
8/4/17 2:29:32:944 CDT] 000000c5 webapp E
com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:
[Servlet Error]-[mvc-dispatcher]: java.lang.NoClassDefFoundError:

Caused by: java.lang.ClassCastException: javax.naming.Reference
incompatible with javax.enterprise.inject.spi.BeanManager
###

LOCAL FIX:
None

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server who do not use CDI but use a third party library that uses jndi to access CDI such as jersey.

PROBLEM DESCRIPTION:
JNDI is returning a Reference object instead of a null when CDI is disabled, resulting in the following exception:
java.lang.ClassCastException: javax.naming.Reference incompatible with javax.enterprise.inject.spi.BeanManager


RECOMMENDATION:
None

PROBLEM CONCLUSION:
An exception which was frequently hit during normal operation was replaced with a logging message. However this change resulted in JNDI returning Reference objects instead of nulls when looking up a BeanManager. To fix this we reverted the change and re-introduced the exceptions.

The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.13. Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980