APAR status
Closed as program error.
Error description
Problem: When using wsinstance command to create was instances
and subsequently to create new app servers for those instances,
conflicting port numbers get generated. The problem has been
reported internally with two defects which will go into PTF 3.
This problem applies to 5.0.2 Base and ND on all platforms.
SENARIO:
1. Using wsinstance, create an instance of a WAS Base install
using a unique startingPort value (say 12400) and call it
wasIB1.
2. Start server1 of instance wasIB1.
3. Using wsadmin, connect to server1 of instance wasIB1 and
create another application server and call it server2
4. From the command line (you can't use wsadmin to do this)
start server2.
5. Using wsinstance, create an instance of a WAS Base install
using a unique startingPort value (say 12500) and call it wasIB2
6. Start server1 of instance wasIB2.
7. Using wsadmin, connect to server1 of instance wasIB2 and
create another application server and call it server3.
8. From the command line, attempt to start server3.
9. The start will fail with a message stating that the server is
already started.
The problem is that both server2 and server3 are being created
with the same port assignments (see the node level
serverindex.xml file and the server level server.xml file).
There is not a way using the wsadmin create function
($AdminConfig create Server) to force generation of unique port
numbers.
This problem can be resolved if during execution of wsintance,
the template's serverindex.xml is updated to reflect the new
port number. The current template's serverindex.xml is simply
copied to the new instance, resulting in the same port number
being used for new servers created for both instances.
Local fix
WORKAROUND:
Create a new server not based on the template, but based on an
existing server.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0.2 users *
* who use wsinstance tool to create *
* multiple WebSphere instances. *
****************************************************************
* PROBLEM DESCRIPTION: Application servers created in a new *
* WebSphere instance contains duplicate *
* port numbers with those in the default *
* WebSphere instance. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
During the creation of a new WebSphere instance, the wsinstance
tool fails to update the template configuration file with the
new port numbers. Later when application servers are created,
duplicate port numbers will be used.
Additionally, wsadmin component changes are required to
correctly generate unique port numbers.
Problem conclusion
Both wsinstance and wsadmin components are modified to
generate unique port numbers when using the wsinstance
command to create WebSphere instances and subsequently to
create new application servers for those instances.
Temporary fix
The test fix, PQ77534, is now available on
PQ99999 site.
Comments
APAR information |
APAR number |
PQ77534 |
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 |
2003-08-15 |
Closed date |
2003-10-06 |
Last modified date |
2004-06-28 |
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 |
R00S PSY |
UP |
R00W PSY |
UP |
|