|
Problem(Abstract) |
Thin client application made a call to a remote server and
got a "Connection refused" exception.
13:17:16.597 com.ibm.rmi.iiop.Connection createInputStream:1014
RT=0:P=227003:O=0:WSTCPTransportConnection[addr=999.88.77.99,port=2809,local=1867]
ORBRas[default] Entry
13:17:17.509 com.ibm.ws.orbimpl.transport.WSTCPTransportConnection
connect:427 Thread-3 ORBRas[default] java.net.ConnectException: Connection
refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.connect(Socket.java:428)
at java.net.Socket.<init>(Socket.java:3350
at java.net.Socket.<init>(Socket.java:150)
Using netstat -an on the server showed the server was listing on port
2809. |
|
|
|
Cause |
ORB
Tracing showed that the server did receive the client request and sent
back a response to the client forwarding it to another server. The
forwarding address was 127.0.0.1 which is a loopback IP address for
localhost.
The client received the forward from the remote server and tried to
connect to itself at 127.0.0.1 causing the connection refused to
occur.
|
|
|
Resolving the
problem |
Change the host entry in serverindex.xml from "localhost"
to the actual hostname for the server.
If WebSphere is federated, back up and update the serverindex.xml of the
deployment manager, synchronize to all nodes, then restart WebSphere. If
the system is a stand-alone server, back up and modify the serverindex.xml
for that server. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Historical Number |
0025
R3K
000 |
|
|
|
|