PQ71171: INCONSISTENT LOADING OF MODULES - WEB MODULES ARE LOADED BEFORE THEY EJB MODULES AT STARTUP.

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Inconsistent loading of Modules.  The tracefile for WebSphere
AppServer shows that the EJB module loads first at startup,
however, the stdout file shows that Web Module loads first.
This inconsistency is caused by asynchronous loading of tasks
(threads) and since the web module (servlets) call the
EJBs that are not completely initiated, it results in a
failure. Synchronization of the tasks will guarantee that
EJB Modules are loaded first before the Web Modules.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0 users.      *
****************************************************************
* PROBLEM DESCRIPTION: Inconsistent loading of modules - web   *
*                      modules loaded before the EJB modules   *
*                      complete load at start-up.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Inconsistent loading of modules - web modules loaded before the
EJB modules complete load at start-up.  Modules are initiated
to load in the correct order, however the task threads to
actually load each module are asynchronous for efficiency.  As
nature of asynchronous thread, we can't guarantee system will
schedule threads in the order we want.
Problem conclusion
Solution is to synchronize threads, however at the cost of
efficiency. Rather than loading the modules in parallel, they
are now loaded serially, which will take longer than before.
For this reason, the synchronization is turned OFF by default,
and will only be turned on as needed by customer.
This test fix applies to WSCP and Admin Console. Customer
should apply this fix on all machines where clients are run.
After applying the fix jar, to turn on sync on WSCP, in the
wscp property file (e.g. create file named wscp.props), add:
    wscp.syncStartModules=true
then restart wscp via
    % wscp.sh -p wscp.props
To turn on sync on Console,
in the $WASHOME/properties/ejsconsole.properties file,
add: ejs.console.syncStartModules=true
Temporary fix
sent fix test packaged in SM cumulative fix for customer to test
Comments
APAR information
APAR number PQ71171
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-02-19
Closed date 2003-04-03
Last modified date 2003-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
NONE AdminSVR        

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ71171
IBM Group: Software Group
Modified date: Apr 3, 2003