PQ75816: Takes long time to start dmgr when a lot of clusters are configured.

 Fixes are available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)
PQ75816, 5.0.0 &5.0.1: Dmgr startup delay when there is a large # of clusters.



APAR status
Closed as program error.

Error description
When a 150 or more clusters are configured, dmgr takes over 70
minutes to start(i.e 40 seconds per cluster).  This problem
was corrected with internal
defect 167405. The ClusterMg.updateClusterObjName() method was
performing a query over the whole cell rather than just the
dmgr.  By limiting the scope of the query to the "dmgr" node,
the startup performance was improved greatly.

Opening Apar to for internal defect.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0 users of    *
*                 Workload Management, Network Deploymnet and  *
*                 the Deployment Manager.                      *
****************************************************************
* PROBLEM DESCRIPTION: The performance of the Deployment       *
*                      Manager is slow when it is started.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the Deployment Manager is started, if there are numerous
clusters configured, the startup process will be slowed by
approximately 40 seconds per cluster.
Problem conclusion
In the ClusterMgr MBean code, which is loaded and started in the
Deployment Manager when the Deployment Manager is started,
invokes an MBean call itself that was not scoped to just the
Deployment Manager process.  The fix to the problem was scoping
the ClusterMgr MBean invokation on another MBean to just the
DMgr process.  Otherwise ,the MBean invokation was sent out to
the node agent process's as well, thus taking longer to complete
then was necessary.
Temporary fix
apar is sent to the customer, waiting for feedback before
closing
Comments
APAR information
APAR number PQ75816
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 00S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-06-30
Closed date 2003-08-26
Last modified date 2003-08-26

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WLM          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ75816
IBM Group: Software Group
Modified date: Aug 26, 2003