Open the wsadmin.traceout. Look at the Mustgather links above for location
of the wsadmin.properties file. The following is an example of a trace you
might see:
This problem can occur because the Application Server to which you are
trying to connect is not running, or you are trying to connect to the
wrong port number.
First, verify and make sure the server is up and running by looking at
the systemout.log file for the server you are trying to connect to.
Second, verify the port that wsadmin is trying to connect to by looking
at the wsadmin.properties file.
|
com.ibm.ws.scripting.host=hostname
com.ibm.ws.scripting.port=8879
|
|
Compare the above port number to the entry in the SystemOut.log from the
application server. This tells you on which port the application server is
actually listening for SOAP connections as shown in example below:
|
[8/15/06 10:22:07:188 EDT] 0000000a
JMXSoapAdapte A ADMC0013I: The SOAP
connector is available at port 8879
|
|
If the host and port are out of sync then your wsadmin.properties file is
out of sync and will need to be modified with the correct hostname and
port number. Use the systemout.log file to retrieve the correct values for
hostname and port number.
You can also use the
telnet command to try and get a connection to
the host name and port:
|
telnet myHostName 8879
Connecting To myHostName...Could not open a connection to host on port
8879 : Connect failed
|
|
Note that even if you can connect, you will not be able to do anything
because Application Server does not respond to telnet commands. You can
close your telnet session by pressing
Ctrl+c.
Alternatively, you can use
-host and
-port arguments as
follows:
|
./wsadmin.sh -host myHostName
-port 8879
|
|
The above arguments will override the values specified in
wsadmin.properties file.