Sendt fra min iPhone
> Den 20. aug. 2015 kl. 21.06 skrev Shushant Arora <[email protected]>: > > A doubt regarding async client - does it sends the request on same > connection before waiting for repose of previous request on same connection No request multiplexing in http 1.1 > ? Or it will reuse the connection only when first request's response has > arrived or request timeouts ? > > Since I doubt connection close is not coming because of server rather > client machine tcp socket connections limit - Same http client with same > pool size to same same server is working fine but giving connection close > exception on another machine. > > > When I saw the value of sysctl net.ipv4.ip_local_port_range > On machine where exceptions are coming its > net.ipv4.ip_local_port_range = 32768 61000 > but on another machibe its net.ipv4.ip_local_port_range = 1024 65500 > >> On Thu, Aug 20, 2015 at 8:40 PM, Oleg Kalnichevski <[email protected]> wrote: >> >>> On Thu, 2015-08-20 at 20:31 +0530, Shushant Arora wrote: >>> but its failing my job .Is there any eviction policy I should be handling >>> or its automatically taken care of evicting the closed connections. >> >> You have not been listening, have you? The server closes the connection >> on its end _prematurely_. >> >> Oleg >> >>>> On Thu, Aug 20, 2015 at 8:02 PM, Oleg Kalnichevski <[email protected]> >>> wrote: >>> >>>>> On Thu, 2015-08-20 at 20:00 +0530, Shushant Arora wrote: >>>>> Unplugging is not possible. >>>>> >>>>> How to capture the exception in code and detect if a connection is >>>> closed - >>>>> don't use it in further requests and create new one in pool (set to >> max >>>>> connnection pool)? >>>> >>>> HttpClient manages persistent connections internally and automatically >>>> discards connections that cannot be re-used. >>>> >>>> Oleg >>>> >>>> >>>>> On Thu, Aug 20, 2015 at 7:55 PM, Oleg Kalnichevski <[email protected] >>> >>>> wrote: >>>>> >>>>>>> On Thu, 2015-08-20 at 19:55 +0530, Shushant Arora wrote: >>>>>>> how to avoid this exception - how to handle this. >>>>>> >>>>>> Unplugging your computer from the network will reliably eliminate >> the >>>>>> problem. >>>>>> >>>>>> Oleg >>>>>> >>>>>>> On Thu, Aug 20, 2015 at 7:45 PM, Oleg Kalnichevski < >> [email protected] >>>>> >>>>>> wrote: >>>>>>> >>>>>>>>> On Thu, 2015-08-20 at 19:43 +0530, Shushant Arora wrote: >>>>>>>>> Hi >>>>>>>>> >>>>>>>>> I am using HttpAsyncClients and >>>> PoolingNHttpClientConnectionManager . >>>>>>>>> Getting below exception when I increase no of http clients on >>>>>> machine. >>>>>>>> What >>>>>>>>> could be the reason and solution for this. >>>>>>>>> >>>>>>>>> >>>>>>>>> org.apache.http.ConnectionClosedException: Connection closed >>>>>>>>> at >> org.apache.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput(HttpAsyncRequestExecutor.java:321) >>>>>>>>> at >>>>>>>> >>>>>>>> The opposite endpoint closed the connection on its end without >>>>>> correctly >>>>>>>> completing the message. >>>>>>>> >>>>>>>> Oleg >>>>>>>> >>>>>>>> >> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:263) >>>>>>>>> at >> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) >>>>>>>>> at >> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:116) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:339) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.SessionInputBufferImpl.fill(SessionInputBufferImpl.java:206) >>>>>>>>> at >> org.apache.http.impl.nio.codecs.AbstractMessageParser.fillBuffer(AbstractMessageParser.java:138) >>>>>>>>> at >> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:243) >>>>>>>>> at >> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) >>>>>>>>> at >> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:116) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164) >>>>>>>>> at >> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:3 >>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: >> [email protected] >>>>>>>> For additional commands, e-mail: >>>> [email protected] >> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: >> [email protected] >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
