PQ50239: XMLCONFIG RUNS SLOW WHEN UPDATING EJBS.


APAR

APAR status
Closed as program error.

Error description
WAS 3.5.4 with 230+ EJBs.  When updating information in the WAS
repository (ie security info), getting extremely poor
performance (6+ minutes per EJB resulting in 8+ hours per node
for update) using XMLConfig.
Local fix
Problem summary
Repetition of reading resources (URI/EJB) and then every
time searching for a particular resouce with in the that
read list is the main cause for this problem.
Problem conclusion
Cached reading of resources, so that it will be done only once.
Accordingly,changed the search technique.
Fixed code in XMLConfig.java, EJBSecurityConfig.java
and URISecurityConfig.java files.
Temporary fix
Comments
APAR information
APAR numberPQ50239
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-07-02
Closed date2001-07-27
Last modified date2001-07-27

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
XMLCFG
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ50239
IBM Group: Software Group
Modified date: 2001-07-27