APAR status
Closed as program error.
Error description
Problem Summary WAS 5.02 ND solaris 8. when wsadmin is used to
stop appserver, the appserver stops in about 1 minute, but
prompt does not come back for at least 30. Same action in
admin console takes only a minute. stopserver.sh from
commandline also fast.
Local fix
Do not use wsadmin to stop or startserver. Use commandline
startsevrer.sh or stopserver.sh
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server V5.x users *
****************************************************************
* PROBLEM DESCRIPTION: In a large scale system, starting and *
* stopping clusters becomes very slow. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a large scale system, many notifications were sent
among the app server, node agent and dmgr to inform the
the app server state change. This resulted in slow response
in node agent and dmgr because the nofications are emitted
and processed in a serial fashion.
Problem conclusion
Improved the scalability of notification handling by spawning
new threads to emit and process notifications.
Temporary fix
ZE fix error
PQ92409 04/08/04
Comments
APAR information |
APAR number |
PQ85891 |
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 |
2004-03-11 |
Closed date |
2004-04-19 |
Last modified date |
2004-08-04 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|