Re: HttpCore NIO IOReactorException

Answered my own question... I've checked the source, and it appears that the same issue affects 4.1 trunk as well. Thanks, Sam On 11 June 2010 13:05, Sam Crawford wrote: > Okay, will do. > > Also, is it still worth trying the latest 4.0.x code? If so, is > /httpcomponents/httpcore/branches/4.

Re: HttpCore NIO IOReactorException

Okay, will do. Also, is it still worth trying the latest 4.0.x code? If so, is /httpcomponents/httpcore/branches/4.0.x the correct location for it in svn? Thanks, Sam On 11 June 2010 13:02, Oleg Kalnichevski wrote: > On Fri, 2010-06-11 at 12:25 +0100, Sam Crawford wrote: >> Well, that was qui

Re: HttpCore NIO IOReactorException

On Fri, 2010-06-11 at 12:25 +0100, Sam Crawford wrote: > Well, that was quick. I can indeed reproduce it by sending an empty > entity enclosing request to the server. The correct "Content-Length: > 0" header is present, so I would have thought this is a valid request, > no? > Yes, the request is

Re: HttpCore NIO IOReactorException

Well, that was quick. I can indeed reproduce it by sending an empty entity enclosing request to the server. The correct "Content-Length: 0" header is present, so I would have thought this is a valid request, no? [...@dev3 ~]$ curl -v -d "" https://proj.acmecorp.com/ * About to connect() to proj.a

Re: HttpCore NIO IOReactorException

On Fri, 2010-06-11 at 11:46 +0100, Sam Crawford wrote: > I should add that we're using HttpCore 4.01. The issue sounds similar > to HTTPCORE-180. > > We're using the following JVM: > > java version "1.6.0_17" > Java(TM) SE Runtime Environment (build 1.6.0_17-b04) > Java HotSpot(TM) 64-Bit Server

Re: HttpCore NIO IOReactorException

Hi Oleg, Thanks for the quick response as always! I should point out that the client causing this exception is outside of our control (indeed I have no idea who rl143.1blu.de is, or what data they're sending). They could well be sending an entity enclosing request without an entity. I'll try to

Re: HttpCore NIO IOReactorException

On Fri, 2010-06-11 at 11:33 +0100, Sam Crawford wrote: > Morning, > > We've just put together our first HttpCore-based server and we're > intermittently seeing an exception in our logs which is causing the > entire server to shutdown. > > INFO com.acmecorp.proj.http.HttpSSLServer: Connection open

Re: HttpCore NIO IOReactorException

I should add that we're using HttpCore 4.01. The issue sounds similar to HTTPCORE-180. We're using the following JVM: java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) Thanks, Sam On 11 June 2010 11:33,

HttpCore NIO IOReactorException

Morning, We've just put together our first HttpCore-based server and we're intermittently seeing an exception in our logs which is causing the entire server to shutdown. INFO com.acmecorp.proj.http.HttpSSLServer: Connection open: [rl143.1blu.de/82.98.78.94:40892] ERROR com.acmecorp.proj.http.Http

RE: same HttpClient object for multiple threads it is not working and causing the exception

I forgot to mention another useful source, the HttpClient tutorial, specifically to your questions you may want to jump directly here: http://hc.apache.org/httpcomponents-client-4.0.1/tutorial/html/connmgmt.html#d4e596 > Hi Rajkumari, > > so far I have not tried HttpClient 4.x on my own, but

RE: Understand cause and properly handle Connection reset

Hi Oleg, thanks again for your answer which somehow confirms my understanding, although I do not really like any of the two options. > Basically, HTTP provides no mechanism to inform the client > that the server is about to close the connection. Yeah, this should be the big underlying problem.