APAR status
Closed as program error.
Error description
When we make a new app server from a template of an existing
app server that already belongs to a cluster, the app server
will not show up on the drop down list of existing app
servers when you try to create an new cluster. Also, the new
app server does not show up as being a member of the cluster
that the template app server belonged to.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server v5.x users *
****************************************************************
* PROBLEM DESCRIPTION: When creating a new server based on an *
* existing server that is also a cluster *
* member, the newly created server also *
* has the cluster reference in its *
* server.xml file. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The cluster reference in the server.xml file comes from the
server configuration file it is based on (a cluster member, in
this case) and is not removed for the new server.
Problem conclusion
Added code to remove the cluster references in server.xml
during server creation.
Temporary fix
test fix available on
PQ99999 site
Comments
APAR information |
APAR number |
PQ84101 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-02-03 |
Closed date |
2004-05-06 |
Last modified date |
2004-05-06 |
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 |
|