Fixes are available
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
CDI is unable to handle a CDI class being dynamically updated, so as a precaution CDI applications will only allow full restarts. Because of that the following exceptions maybe happen: Caused by: java.rmi.RemoteException: ; nested exception is: java.lang.IllegalStateException: Managed Class {com.example.hello.world.service.HelloWorldService} does not match Bean Class {com.example.hello.world.service.HelloWorldService} at com.ibm.ws.cdi.impl.managedobject.CDIEJBManagedObjectFactoryImpl .getBean (CDIEJBManagedObjectFactoryImpl.java:118) at com.ibm.ws.cdi.impl.managedobject.CDIEJBManagedObjectFactoryImpl .createC ontext(CDIEJBManagedObjectFactoryImpl.java:78) at com.ibm.ejs.container.ManagedBeanOBase.createInterceptorsAndInst ance(Man agedBeanOBase.java:191)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: CDI can enter a bad state when a * * single module is updated * **************************************************************** * RECOMMENDATION: * **************************************************************** CDI can end up with stale data when a single module is restarted in an application that uses CDI.
Problem conclusion
CDI now sets a flag on applications that causes a single module restart to trigger a full application restart instead. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.7. 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 number
PI86936
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-07
Closed date
2018-03-09
Last modified date
2019-06-06
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
R900 PSY
UP
Document Information
Modified date:
04 May 2022