Webservice Connection timed out

Webservice Connection timed out

Webservice Connection timed out: When a webservice Connection timeout error occurs, I think the reason is nothing more than that the Connection path between webclient and webservice is abnormal. How can this problem be solved?

I. Error Log

In order to be able to access the seat, Let's first look at the error log:

ERROR 10:40:06, 482 com. honzh. socket. util. exchangeUtil:; nested exception is: java.net. connectException: Connection timed out: connectAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.net. connectException: Connection timed out: connect faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection timed out: connectat java.net. plainSocketImpl. socketConnect (Native Method) at java.net. plainSocketImpl. doConnect (PlainSocketImpl. java: 351) at java.net. plainSocketImpl. connectToAddress (PlainSocketImpl. java: 213) at java.net. plainSocketImpl. connect (PlainSocketImpl. java: 200) at java.net. socksSocketImpl. connect (SocksSocketImpl. java: 366) at java.net. socket. connect (Socket. java: 529)

From the error log, the Code part should be normal and cannot see any errors. In other aspects, it cannot be seen at the moment. This reminds me of the black swan of the online service from Ctrip's fault review, which describes the impact of the percentage of program stability on the server interruption time:

99.9%, service interruption time: 525.6 minutes/year
99.99%, service interruption time: 52.56 minutes/year
99.999%, service interruption time: 5.256 minutes/year

That is to say, the program will always encounter exceptions in unexpected circumstances. When an exception occurs, the most important thing is to maintain a good attitude and find out the cause.

2. Solution ①. Can I access this webservice from other places?

After a webclient is used to access the webservice, it seems that it is not a problem with the webservice server. The problem may occur on the machine where the above error occurs.

② Ping the ip addresses of both parties

I couldn't, and I found that the heartbeat packets of both sides were normal, so let's see if the port is occupied.

③ Netstat-nao

The webservice connection port is also normal and is not occupied by other ports.

④ Telenet ip address and port

If the connection fails, this is definitely a problem. How can this problem be solved? I asked a professional about how to modify the server jump point.

⑤ Jump point

I am not quite clear about the jump point. I will first ask du Niang:

Hop: route. A route is a hop. During transmission, multiple networks are required. Each transmitted network device point (capable of Routing) is called a hop, and the address is its ip address. The number of hops is the number of accumulators passed by. To prevent useless data packets from flowing online. Specify the integer (range: 1 ~ 9999). It is used to select the route that best matches the destination address in the forwarding packet among multiple routes in the routing table. The selected route has the minimum number of hops. The number of hops reflects the quantity, speed, reliability, throughput, and management attributes of the hops.

Well, it's too professional to understand, but you can try it:

After modifying the hop point, connect to webservice and find that the connection is successful. Of course, this is only one solution, and another.

6. Modify the default port number of webservice.

For example, you can change the original 8080 to 8180 and find that the webservice connection is OK. This is of course based on the Skip point that has not been modified.

Tips: Generally, we do not use the default port number, which is vulnerable to attacks and exceptions.