Application server port assignment conflicts with default administrative server port assignment and is not propagated to plugin-cfg.xml
 Technote (troubleshooting)
 
Problem(Abstract)
The tenth application server created is assigned HTTP transport port 9090, which can interfere with the default administrative port. Also, this assignment is not propagated to the plugin-cfg.xml Web server plugin file.
 
Cause
When creating application servers, the HTTP transport port is incremented by 1 for each new application server created. By default, the tenth application server created uses port 9090, which is also used by the administrative console for both ND and Base editions. If this server is not on the same host as the deployment manager and therefore the port does not overlap, it is not propagated to the plugin-cfg.xml file. This is because the admin_host virtual host has this port set and so it will not be added to the plugin-cfg.xml file by design.

If any other ports associated with the admin_host are duplicated, the same problem occurs. For example, if an application server is assigned SSL port 9044, this conflicts with the default admin_host SSL port of 9044.

 
Resolving the problem
There are two solutions for this port conflict:
  • Change the HTTP transport for the tenth application server.

  • Change the administrative port assignment for the admin_host.

Either one allows the HTTP transport for this server to start without conflict, and to be generated into the plugin-cfg.xml file.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1166055
IBM Group: Software Group
Modified date: Apr 14, 2004