PI52756: CDI IS ACTIVATED AND GENERATES ERROR WITH NO EXISTENCE OF BEANS.XML

Fixes are available

APAR status

Closed as program error.

Error description

The application is not using Contexts and Dependency Injection
(CDI), and there is no existence of the beans.xml, but CDI is
activated and generated the following error:

CWOWB0102E: A JCDI error has occurred: JCDI runtime cannot
resolve @Inject method_name because of a null IBMBeanManager

CWNEN0035E: The @Inject method_name reference of type xxx for
the <null> component in the <WAR> module of the application
cannot be resolved.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: The customer wishes to use an           *
*                      alternative to Websphere Application    *
*                      Server's CDI component to handle the    *
*                      @Inject annotation                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The customer wishes to use an alternative CDI component to
handle the @Inject annotation however they cannot because
Websphere Application Server's CDI component throws an
UnsatisfiedResolutionException

Problem conclusion

A new JVM custom property com.ibm.ws.cdi.ignoreInjectionFailure
was created. This property configures Websphere to continue
working after an injection failure. Note that any injection
failures will still be shown in the logs as usual.

To make use of this fix open the administration console. Click
Servers > Server Types > WebSphere application servers >
server_name. And then, under Server Infrastructure, click Java
and process management > Process definition > Java virtual
machine > Custom properties

Finally create a new custom property called
"com.ibm.ws.cdi.ignoreInjectionFailure" and set the value to
true.

Be warned, setting this property to true violates the CDI
specification and should only be used if you are using an
alternative provider to handle the @Inject annotation. For
this reason we recomend the specification complient solution
documented in the Temporary Fix.

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

Temporary fix

This problem can be circumvented by using @Autowired instead
of @Inject as the Spring framework treats the two annotations
as identical but Websphere's CDI component will ignore
@Autowried.

We recommend this solution over setting the custom
property as it is compatible with the specifications.

Comments

APAR Information

APAR number
PI52756
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-18
Closed date
2016-02-17
Last modified date
2016-04-01

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

R700 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI52756: CDI IS ACTIVATED AND GENERATES ERROR WITH NO EXISTENCE OF BEANS.XML

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R850 PSY

Document Information

Share your feedback

Need support?