RE: 'Socket closed' exception using

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.

RE: 'Socket closed' exception using

: RE: 'Socket closed' exception using 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

RE: 'Socket closed' exception using

on the response header prevents the connection from being closed? Thank you, Sofya -Original Message- From: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED] Sent: Friday, May 14, 2004 10:35 AM To: Commons HttpClient Project Subject: RE: 'Socket closed' exception using Sofya, It does sound dubious

RE: 'Socket closed' exception using

To: Commons HttpClient Project Subject: RE: 'Socket closed' exception using 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

RE: 'Socket closed' exception using

Project Subject: Re: 'Socket closed' exception using Hi Sofya, I agree with Oleg, it seems that the server is closing the connection in the middle of a request. Does not this prove that the socket is closed from the application side, i.e from inside the HTTPClient? Or it is possible

Re: 'Socket closed' exception using

How are you setting your headers? That is sometimes the issue on socket closings. At 10:25 AM 5/12/2004, Preygel, Sofya wrote: 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

RE: 'Socket closed' exception using

: Re: 'Socket closed' exception using How are you setting your headers? That is sometimes the issue on socket closings. At 10:25 AM 5/12/2004, Preygel, Sofya wrote: Hello, We are trying to use

RE: 'Socket closed' exception using

: Wednesday, May 12, 2004 1:29 PM To: Commons HttpClient Project Cc: [EMAIL PROTECTED]; Preygel, Sofya Subject: Re: 'Socket closed' exception using How are you setting your headers? That is sometimes the issue on socket closings. At 10:25 AM 5/12/2004, Preygel, Sofya

Re: 'Socket closed' exception using

Hi Sofya, There are a couple of possibilities, but it sounds like you are experiencing some connection management 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

RE: 'Socket closed' exception using

-Original Message- From: Michael Becke [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 4:37 PM To: Commons HttpClient Project Subject: Re: 'Socket closed' exception using Hi Sofya, There are a couple of possibilities, but it sounds like you are experiencing some connection management

RE: 'Socket closed' exception using

: 'Socket closed' exception using Sofya, (1) What's the reason for using HTTP/1.0 if the target server is clearly capable of doing HTTP/1.1? 18:04:53 DEBUG [Thread-17] - POST /WS/AgentLibrary.asp HTTP/1.0[\r][\n

Re: 'Socket closed' exception using

Hi Sofya, I agree with Oleg, it seems that the server is closing the connection in the middle of a request. Does not this prove that the socket is closed from the application side, i.e from inside the HTTPClient? Or it is possible for the HttpConnection.close() to be called when a closed