Sunday Oct 14, 2012

java.net.SocketException: Connection reset; No available router to destination

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:

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
About

Antonio De Juan Image

I was formerly a Senior Technical Support Engineer in the Middleware Application Server Team. I worked supporting Weblogic Server, Java EE, Jrockit, Coherence among other Oracle products.
You can find my new blog at :
http://antoniodejuan.wordpress.com/
Oracle WebLogic

Search

Categories
Archives
« October 2012
SunMonTueWedThuFriSat
 
1
2
3
4
5
6
7
8
10
11
12
13
15
16
17
19
20
21
22
23
24
25
26
27
28
29
30
31
   
       
Today