APAR status
Closed as program error.
Error description
If all of the cluster members get orphaned, the client will
experience CORBA_NO_IMPLEMENT exceptions when attempting to use
EJB's deployed to the cluster
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* Workload Management (WLM) or Clustering. *
****************************************************************
* PROBLEM DESCRIPTION: In a large WebSphere cell, cluster *
* members get orphaned when the *
* Deployment Manager gets overloaded *
* during cell startup. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In a large WebSphere cell, cluster members get orphaned when
the Deployment Manager gets overloaded during cell startup. A
symptom of this is the client may receive a No_Implement
exception even though the cluster appears to be started. Then
by restarting a cluster member in the cluster, that cluster
member gets routed to, but none of the other cluster member
are routed to yet.
Problem conclusion
A thread needed to be spawned off to help handle the load
in the Deployment Manager better.
Temporary fix
Restart the effected cluster.
Comments
APAR information |
APAR number |
PQ89072 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-05-19 |
Closed date |
2004-07-21 |
Last modified date |
2004-07-21 |
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 |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|