Fixes are available
APAR status
Closed as program error.
Error description
ServletContextListener is unable to call an EJB. It turns out that they are inadvertantly using EJB-in-WAR, but this also points out that we are stopping the EJB portion of a WAR before stopping the WAR portion. This is backwards from the default of always stopping EJB modules after WAR modules. ApplicationMgrImpl.stop(DOE) should probably either reverse the order it calls the handlers, or start(DOE) should use an ArrayDeque and addFirst.
Local fix
No work around provided at this time.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: In an EJB-in-WAR scenario, the * * application manager stops the EJB * * first, so the WAR sees an exception * * when it stops. * **************************************************************** * RECOMMENDATION: * **************************************************************** The WebSphere Application Server application manager stops the application's object handlers in the order they were started - EJB, then WAR. In the case of an application that contains an EJB within a WAR, the EJB was then stopped first, despite the fact that it may still be referenced by the WAR, resulting in an exception.
Problem conclusion
The order in which the handlers are stopped was reversed, so the EJBs are now correctly stopped after the associated web modules. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.11. 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
PI23974
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-08-15
Closed date
2014-12-16
Last modified date
2014-12-16
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
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021