Fix (APAR): PI55574 Status: Fix Release: 8.5.5.8,8.5.5.7,8.5.5.6,8.5.5.5,8.5.5.4,8.5.5.3,8.5.5.2 Operating System: AIX,HP-UX,IBM i,Inspur K-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 292436 Date: 2016-07-21 Abstract: handlers start in incorrect order when provisioning is enabled Description/symptom of problem: PI55574 resolves the following problem: ERROR DESCRIPTION: Handlers start in incorrect order when provisioning is enabled LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server PROBLEM DESCRIPTION: Modules are started in an incorrect order when Application Server setting "start components as needed" is enabled. RECOMMENDATION: None For Java EE applications that contain an EJB within a WAR module, the application manager calls to containers to process that module in a specific order - first the EJB container, then the web container. In environments with runtime provisioning (the "start components as needed" setting) and a set of applications that includes web-only application(s) in addition to the EJB-in-WAR application, it is possible for the EJB handler to be registered after the web handler, resulting in the module being processed incorrectly and potentially leading to failures when code in the WAR attempts to reference the EJB. PROBLEM CONCLUSION: Additional logic was added to handle this scenario and prevent out-of-order handler registration. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.11 and 9.0.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 8.5 X_ Application Server (Express or BASE) X_ Network Deployment (ND) __ Liberty Core __ Edge Components __ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required. The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before applying the iFixes. Restart WebSphere Application Server after applying the iFixes. Directions to remove fix: The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before removing the iFixes. Restart WebSphere Application Server after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: