Fixes are available
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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 an ActivationSpec resource is stopped before the corresponding message-driven bean application is stopped, then the EJB container detects the order of events as being invalid, and creates an FFDC log for an IllegalStateException. The IllegalStateException is never actually thrown and both the ActivationSpec and message endpoint do shutdown properly. The expected order of shutdown for a message-driven bean is very specific for a full profile server, but when a Liberty profile server is stopped, the various resources in use will be stopped asynchronously, so the order of shutdown events will vary.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile with message-driven * * bean applications * **************************************************************** * PROBLEM DESCRIPTION: Intermittent FFDC of * * IllegalStateException when stopping a * * Liberty profile server with a message- * * driven bean application * **************************************************************** * RECOMMENDATION: * **************************************************************** If an ActivationSpec resource is stopped before the corresponding message-driven bean application is stopped, then the EJB container detects the order of events as being invalid, and creates an FFDC log for an IllegalStateException. The IllegalStateException is never actually thrown and both the ActivationSpec and message endpoint do shutdown properly. The expected order of shutdown for a message-driven bean is very specific for a full profile server, but when a Liberty profile server is stopped, the various resources in use will be stopped asynchronously, so the order of shutdown events will vary.
Problem conclusion
The EJB container has been updated to support message-driven beans applications and the corresponding resources shutting down in any order. An FFDC log for the IllegalStateException will no longer occur when stopping a Liberty Profile server with a message-driven bean application. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.5. 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
PI27706
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-15
Closed date
2014-10-23
Last modified date
2014-10-23
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
Document Information
Modified date:
28 April 2022