|
Problem(Abstract) |
Attempting to start the sixth deploymentmanager installed
on the same machine. The systemout.log shows:
WSVR0221I: Application started: adminconsole
SRVE0171I: Transport http is listening on port 9,095.
SRVE0171I: Transport https is listening on port 9,048.
ADMC0026I: RMI Connector available at port 2814
WSVR0001I: Server dmgr open for e-business
Error: can not create registry on port 19,099.
SRVE0172I: Stopped transport http on port 9,095.
SRVE0172I: Stopped transport https on port 9,048.
WSVR0217I: Stopping application: adminconsole
SRVE0170I: Stopping Web Module: adminconsole.
|
|
|
The first five dmgr's use ports 14,099, 15,099, 16099,
17,099 and 18,099. The sixth dmgr is attempting to use 19,099 which is
also being used by wlm.controller.jar.
For functionality, the wlm.controller.jar file was originally shipped as
part of a workload management enhancement to provide dynamic load
balancing.
It is a deprecated function because dynamic load balancing is no longer
enabled in base Websphere or Websphere Network Deployment, but instead is
in WebSphere Extended Development.
It causes a port conflict problem because it opens ports to communicate
with application servers. It can be removed because it is a deprecated
function.
Dynamic load balancing comes with Extended Development. For base and
Network Deployment, standard WLM is enabled.
The problem is only seen on WebSphere Business Integration Server
Foundation V5.0.
|