APAR status |
Closed as program error.
| Error description
When running in a multi-node environment and one of the nodes
goes down, the admin console continues to attempt to contact
the down'ed node for various user operations. This results
in performance problems because the user must wait for the
connection timeout in order for the operation to complete. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Advanced *
* Edition 3.5-3.5.5 users with multinode *
* environments *
****************************************************************
* PROBLEM DESCRIPTION: When in a multi-node environment and *
* one node goes down, performance of *
* admin console is very slow. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Performance was degraded because admin console was continuing
to attempt to contact downed node to obtain active attributes
during various operations. Problem conclusion
Admin server was modified to mark a node "down" and prevent
future attempts to contact the node via the admin console
after detecting node down 1st time. Node remains down until
manually reconnected using admin console, thus minimizing
performance impacts. Temporary fixComments
APAR information | APAR number | PQ54963 | Reported component name | WEBSPHERE AE SO | Reported component ID | 5630A2202 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-11-18 | Closed date | 2002-01-31 | Last modified date | 2002-01-31 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|