You are viewing a plain text version of this content. The canonical link for it is here.

Posted to soap-user@ws.apache.org by Ackerl Werner <Ac...@ubavie.gv.at> on 2002/04/10 17:22:43 UTC

proxy timeout

one of my calls triggers a lengthy database 
operation on the server (140-240sec).

connecting directly, the client waits for the response. 
but when i have to go though a proxy, the call times 
out too fast. 
strange thing is, the time factor seems to depend
on the client.

apache soap,   http:   30 sec
apache soap,   https: 120 sec *
perl soaplite, http:  180 sec
perl soaplite, https: 180 sec

*(this combination was also tested and time confirmed
by one of our testers, on a different proxy)

i even tried SOAPHTTPConnection.setTimeout; but that 
didn't change anything. (i didn't expext it to, but 
my boss insisted).

ah, yes: the errormessages themselves:
apache soap + http says
<HEAD><TITLE>Connection Timed Out</TITLE></HEAD> 
<BODY BGCOLOR="white" FGCOLOR="black"><H1>Connection Timed Out</H1><HR> 
<FONT FACE="Helvetica,Arial"><B> 
Description: Connection Timed Out</B></FONT> 
<HR> 
<!-- default "Connection Timed Out" response (504) --> 
</BODY> 

perl + soaplite says
500 read timeout 

what's going on here?