Re: socket timeout

[Linus Kamb]

So, following the advice in the discussion of this bug, I've cast the client side 
stub to an axis Stub and set the timeout to 600000 milliseconds. (Also tried 0.)

Now I get the following:

[EMAIL PROTECTED]
[EMAIL PROTECTED]
AxisFault
 faultCode: {http://xml.apache.org/axis/}HTTP
 faultSubcode:
 faultString: (0)null
 faultActor:
 faultNode:
 faultDetail:
        {}:return code:  0

(0)null
        at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:630)
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128)
        at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
        at org.apache.axis.client.Call.invoke(Call.java:2553)
        at org.apache.axis.client.Call.invoke(Call.java:2248)
        at org.apache.axis.client.Call.invoke(Call.java:2171)
        at org.apache.axis.client.Call.invoke(Call.java:1691)
        at 
org.scec.cme.velocityServices.VelocityServiceStub.getVelocityForVolume(VelocityServiceStub.java:346)
        at VMClient.doGetVolume(VMClient.java:581)
        at VMClient.main(VMClient.java:692)

13.64u 1.11s 5:21.09 4.5%

This is different (obviously) from the SocketTimeout exception I was getting after 60 
seconds that I was getting before setting the timeout value.

I am using the 7/24 nightly build.

It appears that the client is getting a return code of 0 or maybe just nothing.

Could the server side be closing the socket?

The web service is still working on it's long-running process when the client returns 
with the error.

thanks,
Linus
Laenzlinger, Christof wrote:
I don't know what Axis version you were using before you
downloaded the nightly build.
Have a look at:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18277
and the axis-dev mailing list for recent discussion about
socket timeout.
-----Original Message-----
From: Linus Kamb [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2003 11:46 PM
To: [EMAIL PROTECTED]
Subject: socket timeout
I just downloaded and built and deployed last night's nightly release in 
hopes of
fixing my 3 minutes of marshal/transport/unmarshall time (well, I don't 
know exactly
where it is, but it is somewhere after my service method exits and my 
client's call
returns...)

Now I get a socket timeout on the client side in a little over a minute.

Did something change?  Did I inadvertently change something?

Can I / should I access the MessageContext and set the timeout myself?

Linus

--
Linus Kamb
[EMAIL PROTECTED]
(206) 547-0393 x106


--
Linus Kamb
[EMAIL PROTECTED]
(206) 547-0393 x106