WebSphere 5.0 Port conflict with WS Admin Tool when the Deployment Manager is on the same server as the AppServer.
 Technote (troubleshooting)
 
Problem(Abstract)
After the install of Deployment Manager, the user gets the following error when starting the WS Admin tool:

WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException

WASX7213I: This scripting client is not connected to a server process; please refer to the log file C:\WAS5\DeploymentManager\logs\wsadmin.traceout for additional information.

After the install of Deployment Manager, the wsadmin.properties has com.ibm.ws.scripting.port=8879 and the SOAP port on the Deployment Manager is 8889.
 
Resolving the problem
The problem is resolved by changing the com.ibm.ws.scripting port in the wsadmin.properties to port=8889.
The changes to the wsadmin.properties file are in bold print.

# The port property determines what port is used when attempting
# a connection.
# The default SOAP port for a cell manager is 8879
#com.ibm.ws.scripting.port=8879
com.ibm.ws.scripting.port=8889
#com.ibm.ws.scripting.port=2809

The original file had ws.scripting.port=8879.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
Historical Number
81353 b379
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1173434
IBM Group: Software Group
Modified date: Jul 1, 2004