Re: AW: Connection reset when not using tcpmonitor

Mon, 05 Nov 2012 10:18:05 -0800 

Hi Josef, thanks for your reply.
I tested with Wireshark and it seems that my client is sending exactly the same xml with or without tcpmonitor. I really don't know why when I use the same client using tcpmonitor it works, while when I try directly to webservice it does not work. 


But I found a strange thing. When I configure tcpmonitor to tcp instead 
off http I get the same error.



So. It seems that my client is sending message throught tcp and the 
server accepts only http.



Is it possible that my client is using tcp instead of http to send the 
messages to the server?

If so how can I solve it?

Thanks in advance


PS: The server is ASP .net and the client is axis and the beans were 
made using Eclipse




*Humberto Costa de Santana*
Grupo de Desenvolvimento de Sistemas - AI - Reitoria
Em 01-11-2012 07:18, Stadelmann Josef escreveu:


1. I would look at the stack trace below;

faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

"Server.userException", so the origin is somewhat clear! It is 
generated at the server/service side of the pond for whatever reason.
If this happens at the service, then it has potentially nothing to do 
with your client code.
Try to find the condition and place in code where this 
Server.userException is generated?



2.I would use a Network Protocol Analyzer like Wireshark and lookout 
for a TCP RST issued sometimes by Windows.



3.In the past we observed this TCP RST signal may times with 
Wireshark, and we could see a distributed NetBeans plugin fail, 
loosing connection as FTP client to its remote FTP server. Then 
engineering hat to deal with that and make a new plugin which was able 
to recover from this situation on a TCP RST.



4.if TCP RST (RESET) is not observed then it might be one of the many 
time outs one can adjust i.e. for Tomcat.


Josef

*Von:*Humberto Costa de Santana [mailto:humbe...@reitoria.unesp.br]
*Gesendet:* Mittwoch, 31. Oktober 2012 17:19
*An:* java-user@axis.apache.org
*Betreff:* Connection reset when not using tcpmonitor

I'm facing a very strange problem when consuming a webservice.


When I consume the webservice using tcpmonitor it works fine. But when 
I use the real url I have the following problem:


Exception in thread "main" AxisFault

 faultCode: 
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode:
 faultString: java.net.SocketException: Connection reset
 faultActor:
 faultNode:
 faultDetail:

    {http://xml.apache.org/axis/}stackTrace:java.net.SocketException: 
Connection reset

    at java.net.SocketInputStream.read(SocketInputStream.java:189)
    at java.net.SocketInputStream.read(SocketInputStream.java:121)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:254)

    at 
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
    at 
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
    at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)

    at 
net.tandberg._2004._02.tms.external.booking.BookingServiceSoapStub.saveConference(BookingServiceSoapStub.java:681)

    at test.client.TesteBooking.main(TesteBooking.java:51)

Does somebody know what is happening?

Thanks in advance

--
*Humberto Costa de Santana*
Grupo de Desenvolvimento de Sistemas - AI - Reitoria

























					Reply via email to