PQ92329: PERFORMANCE ISSUES AT THE ADMINISTRATIVE CONSOLE WHEN A CUSTOMERHAS A LARGE CELL SIZE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer experiences performance degradation due to a large
Cell size (i.e., a Cell with over 50 servers per Node). The
areas that show performance issues are as follows:
(1) Login to the administrative console
(2) Overall administrative console page load
(3) General Node Synchronization
(4) Node Synchronization after deployment of a large application
(i.e., an application with more than 40 modules)
Local fix
Reduce the number of servers per node.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: This APAR Addresses performance         *
*                      concerns using the Administrative       *
*                      Console and during Node                 *
*                      Synchronization.  Login on a large cell *
*                      configurition took over 3 minutes.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Administrative Console appeared sluggish, and simple
operations took a great deal of time.  (ie: a login taking
3 minutes, a node synchronization for 2 nodes taking 30).
Problem conclusion
Administrative Console:
When logging into the Administrative Console a cell
wide snapshot of the config is taken, to perform
this the entire config needed to be queried.  The
code for accessing the cell configuration was optimized
This provided both fast login, and improvements in general page
responsiveness.

Node Synchronization:
   Transformer:
   The Transformer was optimized for larger
   configurations.  It was changed to build
   the was.env files for servers in a parallel fashion.
   The generation of was.env files is done at the tail
   end of the Node Synchronization process.

   Node Sync:
   When a config change is made on a cell that
   spans multiple nodes and the "Synchronize with Nodes"
   checkbox is chosen on the Administrative Console, each
   node is synchronized one at a time.  The Node Sync
   code was optimized to perform the sync across all
   Node Agents in the cell simultaneously.

   Status Cache:
   The Status Caches are used to hold the status of
   various artifacts in the cell
   (ie: server, application, cluster, message port)
   These caches are driven during Node Sync.  They
   code to drive these was moved off the main thread, as
   the Node Sync did not rely on the output of the Status
   Caches.

APAR PQ92329 is associated with SERVICE LEVEL W502016 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ92329
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-08-03
Closed date 2004-10-07
Last modified date 2004-11-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ93132

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ93769    UP04/10/15 P F410

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ92329.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ92329
IBM Group: Software Group
Modified date: Nov 1, 2004