When using wsinstance command to create WebSphere
Application Server instances and subsequently to create new app servers
for those instances, conflicting port numbers get generate
Download Description
When using wsinstance command to create IBM® WebSphere® Application
Server instances and subsequently to create new application servers for
those instances, conflicting port numbers get generated. The problem has
been reported internally with two defects which will go into Fix Pack 3
for version 5.0.
This problem applies to WebSphere Application Server 5.0.2 Base and
Network Deployment on all platforms.
SCENARIO:
1. Using wsinstance, create an instance of a WebSphere Application Server
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 cannot use wsadmin to do this) start
server2.
5. Using wsinstance, create an instance of a WebSphere Application Server
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.
USERS AFFECTED: WebSphere Application Server 5.0.2 users who use
wsinstance tool to create multiple WebSphere instances.
Prerequisites
WebSphere Application Server (Base and Network Deployment) 5.0.2 or
5.0.2.1