hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Sutton <adrian.sut...@ephox.com>
Subject RE: About Bug 14005, HttpMultiClient reusing closed connection, a dvice needed
Date Thu, 28 Nov 2002 22:43:18 GMT
>Also It's a little weird : I only got the bug when I tried to port my
webapp
>under a unix (AIX platform) and making requests to this same unix server.
>
>Under Windows, the connection seems to be well closed between servers, even
>distant...
>
>Does anyone have an explanation ? Is there a config file I missed somewhere
>(Using tomcat 4.1.12, jdk 1.3.1) ?
>I didn't change any of the default conf file for tomcat (as under windows),
>but I didn't install the jdk myself, can it be inside jdk itself ?

The problem is occurring because the server times out the connection so the
problem is almost always a configuration setting somewhere.  It may however
not be a configuration in the server itself, the firewall can be configured
to time out connections as well etc.  My first step in debugging any problem
with HttpClient is to telnet into port 80 of the server myself so I can see
exactly what's going on and get a lot more control.  Enabling the http wire
logs are also good but I find the output of telnet is easier to follow and
lets me change around what's sent a bit more easily.

Basically though, it will happen on both servers if you leave it long enough
- it's only a matter of time... (queue spooky music).

Not much more detail I can shed on the situation I'm afraid.

Adrian Sutton, Software Engineer
Ephox Corporation
www.ephox.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom they are addressed. Opinions
contained in this email do not necessarily reflect the opinions of Ephox
Corporation. 
If you have received this email in error please notify the sender
immediately and delete all copies of the correspondence from your computer
and/or computer network. No warranty is given that this message upon its
receipt is virus free and the sender in this respect accepts no liability.

Mime
View raw message