PQ70085: WEB MODULE ARE LOADED BEFORE EJB JARS | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description If the Application Server is started the Web Modules are started before the EJB jars are started. This is the opposite of what should occur. The problem does not normally exist but an installation can get into this state. Note that it is not guaranteed that the EJB jars will be completely loaded before the start of the loading of Web Modules. What is expected is for the EJB jars loading should be initiated before loading the Web Modules in each specific EAR. In this APAR the Web Modules load was initiated before the EJB j loading for a specific EAR. This behavior is evident in the Application Servers stdout file. The stdout will log "Loading Web Module" before logging "Starting EJB jar". Again both the Web Module and the EJB jar are from the same EAR. ServletEngine A SRVE0169I: Loading Web Module: MyWAR. EJBEngine I WSVR0037I: Starting EJB jar: MyEJB The workaround is to start the Enterprise Application from the Admin Console or a script instead of starting the Application Server. This behavior was reported by one site after upgrading the WebSphere fixpack from 4.0.2 to 4.0.3Local fix The workaround is to start the Enterprise Application from the Admin Console or a script instead of starting the Application ServerProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server AE users who * * upgrade from 4.0.2 to 4.0.3 * **************************************************************** * PROBLEM DESCRIPTION: If the Application Server is started * * the Web Modules sometimes are started * * before the EJB jars are started. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the Application Server is started the Web Modules are started before the EJB jars are started. This is the opposite of what should occur. The problem does not normally exist but an installation can get into this state. If start Application (rather than start from the server) then EJB modules are initiated to load before Web modules.Problem conclusion The fix ensures if application is started from the Application Server, EJB modules are initiated to load before Web Modules. Note that it is not guaranteed that the EJB jars will be completely loaded before the start of the loading of Web Modules. What is expected is for the EJB jars loading should be initiated before loading the Web Modules in each specific EAR.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ70085
IBM Group: Software Group
Modified date: Feb 4, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.