Good morning,
I am still working on the 'socket connection' problem. According to the
Connotate tech support a possible reason of getting this exception is
that the connection is not being closed on the client, but instead,
released to the pool:
The socket closure is happening on the WMS side.
once the response is consumed.
See if that helps circumvent the problem.
Hope this helps a little
Oleg
-Original Message-
From: Preygel, Sofya [mailto:[EMAIL PROTECTED]
Sent: Friday, May 14, 2004 16:03
To: Commons HttpClient Project
Subject: RE: 'Socket closed' exception using
Good
Thank you, guys. I will work in this direction, i.e. investigating what
the Connotate's software does with the response, and let you know the
results.
Sofya
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 9:44 PM
To: Commons HttpClient
Hello,
We are trying to use HTTPClient.execute(PostMethod) for sending SOAP
requests to Connotate's Web Mining Server (WMS). The requests are sent
every 1 minute, and in most cases everything works fine. However, every
so often (sometimes way too often!) we are getting the 'Socket closed'
little sense for HTTP 1.0), but to no avail.
Thanks,
Sofya
-Original Message-
From: Michael McGrady [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 1:29 PM
To: Commons HttpClient Project
Cc: [EMAIL PROTECTED]; Preygel, Sofya
Subject
issues. If you could, please
send some sample code showing how you are using HttpClient, as well as a
wire log http://jakarta.apache.org/commons/httpclient/logging.html
(just the headers please).
Mike
Preygel, Sofya wrote:
Hello,
We are trying to use HTTPClient.execute(PostMethod
as
HttpClient is done sending the request body (to be more precise while
flushing the output buffer). That makes me believe that the server is
the most likely culprit, not HttpClient
Oleg
On Thu, 2004-05-13 at 00:09, Preygel, Sofya
