APAR status
Closed as program error.
Error description
Cluster member does not get removed from app server list. This
problem seems to be noticed under WebSphere 5.1.1 and above.
Following configuration setup: Two Nodes
Node A - waslinux21 - ND/BASE WAS 5.1.1
Node B - w2003eserver - BASE WAS 5.1.1
Created cluster - clusterA - and two member clusterA_server1 on
node waslinux21 and clusterA_server1 on node w2003eserver
Run the jython syntax as follow:
Print statement shows both member exits in configuration.
wsadmin>print AdminConfig.list('ClusterMember')
clusterA_server1(cells/waslinux21Network/clusters/clusterA:clust
er.xml#ClusterMember_1089141327698)
clusterA_server1(cells/waslinux21Network/clusters/clusterA:clust
er.xml#ClusterMember_1089141350697)
Remove one member from configuration as shown
wsadmin>AdminConfig.remove('clusterA_server1(cells/waslinux21Net
work/clusters/clusterA:cluster.xml#ClusterMember_1089141327698)'
)''
View the list of member- it shows that one member removed.
wsadmin>print AdminConfig.list('ClusterMember')
clusterA_server1(cells/waslinux21Network/clusters/clusterA:clust
er.xml#ClusterMember_1089141350697)
Save the configuration.
wsadmin>AdminConfig.save()
''
wsadmin>
- Went back to adminconsole -
Servers -> Clusters -> (cluster name) -> cluster members -> this
shows that one cluster member removed.
Went back to
Servers -> Application Servers -> This is the problem - here I
see that cluster member that I removed using jython still
showing in list. These APAR fix this problem.
Local fix
manually remove from adminconsole
Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users *
* who try to remove cluster members *
* from wsadmin. *
****************************************************************
* PROBLEM DESCRIPTION: When removing a cluster using wsadmin, *
* the cluster is removed but, the *
* cluster members remain in the *
* appserver list. When doing this via *
* the admin console the cluster *
* and all its members are removed. *
* *
* This worked at 5.1.0.1 but *
* not since upgrading to 5.1.1 *
* This is the side affect *
* of
PQ88179 *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When removing a cluster using wsadmin the cluster member remains
in the appserver list
$AdminConfig list ClusterMember
$AdminConfig remove <cluster defination>
$AdminConfig save
Then if you check in the administrative console the cluster
member will be deleted but in the appserver list that member
will still be present
Problem conclusion
Changed concerned code to make sure that servers are deleted
from both the Application server list and the cluster member
list in the admin console if a cluster is deleted from wsadmin.
The fix for this APAR is currently targeted for
inclusion in fixpack 5.0.2.10 and 5.1.1.3.
Please refer to the Recommended Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980"
Temporary fix Comments
APAR information |
APAR number |
PQ95798 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-10-15 |
Closed date |
2004-12-09 |
Last modified date |
2004-12-09 |
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 |
|