Oleg,
thank you for getting in touch.
I validated that version that I use is 4.0 GA.
Stuff that I've mentioned is the test that we use to check how
http-async-client works with our code. Unfortunately test is manual so we
don't run it too often. I am sure that this test worked after you provided
the fix for HTTPASYNC-51. We picked the fix from from the source tree build
and our test ran without problem it was beta4 with your fix. Now with 4.0
GA it fails.
Please let me know what more details we can provide. Reproducible case
would require you to have Exchange server installed so I am not sure how
realistic is that.
Thank you,
Alex Oscherov
On Sat, Jan 4, 2014 at 5:48 AM, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Fri, 2014-01-03 at 15:04 -0800, Alex Oscherov wrote:
> > I have a problem making http async client working with Exchange server
> > through IIS 7.5. It looks very similar to HTTPASYNC-51 but now it has
> > nothing to do with authentication. When I send relatively small request
> > everything works fine but large requests fail with
> > ConnectionShutdownException. Below is logging for successful and
> > unsuccessful runs (Unsuccessful run is about 20 times larger than
> > successful one)
>
> ...
>
> > 2014/01/03 15:02:52:793 PST [DEBUG] ManagedNHttpClientConnectionImpl -
> > http-outgoing-0
> > 10.0.115.48:10423<->10.224.203.221:443
> [ACTIVE][r:rw][ACTIVE][r][NOT_HANDSHAKING][0][0][0][0]:
> > Close
> > 2014/01/03 15:02:52:794 PST [DEBUG] MainClientExec - [exchange: 1]
> > Connection can be kept alive indefinitely
> > 2014/01/03 15:02:52:794 PST [DEBUG] InternalHttpAsyncClient - [exchange:
> 1]
> > releasing connection
> > 2014/01/03 15:02:52:794 PST [DEBUG] ManagedNHttpClientConnectionImpl -
> > http-outgoing-0
> > 10.0.115.48:10423<->10.224.203.221:443
> [ACTIVE][rw:rw][CLOSING][r][NEED_WRAP][0][0][0][0]:
> > Remove attribute http.nio.exchange-handler
> > 2014/01/03 15:02:52:794 PST [DEBUG] PoolingNHttpClientConnectionManager -
> > Connection released: [id: http-outgoing-0][route:
> > {s}->https://mc-ex4-1-sfm.s2x.uncrap.local:443][total kept alive: 0;
> route
> > allocated: 0 of 2; total allocated: 0 of 20]
> > 2014/01/03 15:02:52:795 PST [DEBUG] ManagedNHttpClientConnectionImpl -
> > http-outgoing-0
> > 10.0.115.48:10423<->10.224.203.221:443
> [ACTIVE][rw:rw][CLOSING][r][NEED_WRAP][0][0][0][0]:
> > Shutdown
> > 2014/01/03 15:02:52:795 PST [DEBUG] HttpAsyncRequestExecutor - null
> >
> <org.apache.http.impl.conn.ConnectionShutdownException>org.apache.http.impl.conn.ConnectionShutdownException
> > at
> org.apache.http.impl.nio.conn.CPoolProxy.invoke(CPoolProxy.java:133)
> > at com.sun.proxy.$Proxy7.requestOutput(Unknown Source)
> > at
> >
> org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:180)
> > at
> >
> org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:349)
> > at
> >
> org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:236)
> > at
> >
> org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor.inputReady(LoggingAsyncRequestExecutor.java:87)
> > at
> >
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:267)
> > at
> >
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:73)
> > at
> >
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:37)
> > at
> >
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:120)
> > at
> >
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:159)
> > at
> >
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:338)
> > at
> >
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:316)
> > at
> >
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:277)
> > at
> >
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:105)
> > at
> >
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:584)
> > at java.lang.Thread.run(Thread.java:722)
> >
> > 2014/01/03 15:02:52:796 PST [DEBUG] HttpAsyncRequestExecutor -
> > http-outgoing-0 [CLOSED]: Disconnected
> >
> >
>
> First off, what version of HttpAsyncClient are you using? Make sure it
> is the latest (4.0 GA).
>
> For some reason the connection gets closed (see snippet above) even
> though it is perfectly re-usable. This prevents the client exchange
> handler from completing the exchange. It can either be a bug in
> HttpAsyncClient or something in your code. I cannot say more without
> more details or a reproducible test case.
>
> > I am positively sure that this stuff was working couple month ago.
> >
>
> Exactly what stuff? What exactly has changed in the meantime?
>
> Oleg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
> For additional commands, e-mail: httpclient-users-h...@hc.apache.org
>
>
