This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

diagnose opening connection errors

0

Newbie question.

I'm trying to diagnose why a Java-based app runs for a while as a client making SOAP webservice calls, and then starts hitting an exception whereby it cannot open a socket. The OS is Windows 2003 server SP1.

I suspect that there's an error in the way that the client-side API is being used (Axis2 v1.4), such that it fails to recycle some internal resource. Once we hit the condition of not being able to open a socket, we have to restart the Java app.

I'm wondering if we can use Wireshark to help diagnose the problem from an OS/network standpoint?

for information, our Java stack trace is: Caused by:

java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:239)

Many thanks for any insight. Dan Haywood

asked 17 Oct '11, 04:04

danhaywood's gravatar image

danhaywood
1111
accept rate: 0%

edited 18 Oct '11, 23:56

SYN-bit's gravatar image

SYN-bit ♦♦
17.1k957245