java.net.SocketException: Connection reset; No available router to destination
Posted
by adejuanc
on Oracle Blogs
See other posts from Oracle Blogs
or by adejuanc
Published on Sun, 14 Oct 2012 16:54:54 +0000
Indexed on
2012/10/14
21:44 UTC
Read the original article
Hit count: 328
Filed under:
/Oracle
Sometimes a Weblogic Server will be unreachable, there could be several reasons,
the server is hang, down, and thus not responding to a ping, or it could
be related to a network issue.
A possible point of failure in the network layer are firewalls.
You should contact your network team if you have following messages:
A possible work around for the ping command is to use the HTTP protocol, instead of the t3 protocol.
To enable this you must configure WebLogic to do HTTP tunneling.
To enable, access the administration console, click servers-> server you want to reach-> protocols -> http -> enable Tunneling.
no restart is necessary.
And then, following command will work:
A possible point of failure in the network layer are firewalls.
You should contact your network team if you have following messages:
java weblogic.Admin -adminurl t3://adminServer.mydomain.com:7777 -username admin -password lockdown PING
Failed to connect to t3://adminServer.mydomain.com:7777: Destination unreachable; nested exception is:
java.net.SocketException: Connection reset; No available router to destination
A possible work around for the ping command is to use the HTTP protocol, instead of the t3 protocol.
To enable this you must configure WebLogic to do HTTP tunneling.
To enable, access the administration console, click servers-> server you want to reach-> protocols -> http -> enable Tunneling.
no restart is necessary.
And then, following command will work:
java weblogic.Admin -adminurl http://adminServer.mydomain.com:7777 -username igmadmin -password l0ckdown PING© Oracle Blogs or respective owner
