Hi, Sure I will reproduce it using a simple program and get back to you. If it convenient here's a stack trace when it happened.
*java.lang.Exception: Stack trace* * at java.lang.Thread.dumpStack(Thread.java:1329)* * at lk.uom.test.transport.http.nio.custom.sender.SendActionCallback.cancelled(SendActionCallback.java:102)* * at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:150)* * at org.apache.http.nio.protocol.HttpAsyncRequester$RequestExecutionCallback.cancelled(HttpAsyncRequester.java:571)* * at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:150)* * at org.apache.http.concurrent.BasicFuture.cancel(BasicFuture.java:157)* * at org.apache.http.nio.protocol.BasicAsyncClientExchangeHandler.close(BasicAsyncClientExchangeHandler.java:142)* * at org.apache.http.nio.protocol.HttpAsyncRequester.initExecution(HttpAsyncRequester.java:166)* * at org.apache.http.nio.protocol.HttpAsyncRequester.access$200(HttpAsyncRequester.java:63)* * at org.apache.http.nio.protocol.HttpAsyncRequester$ConnRequestCallback.completed(HttpAsyncRequester.java:418)* * at org.apache.http.nio.protocol.HttpAsyncRequester$ConnRequestCallback.completed(HttpAsyncRequester.java:385)* * at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119)* * at org.apache.http.nio.pool.AbstractNIOConnPool.fireCallbacks(AbstractNIOConnPool.java:468)* * at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:287)* * at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:259)* * at lk.uom.test.transport.http.nio.custom.sender.UOMHttpNIOConnPool.lease(UOMHttpNIOConnPool.java:83)* * at lk.uom.test.transport.http.nio.custom.sender.UOMHttpNIOConnPool.lease(UOMHttpNIOConnPool.java:42)* * at org.apache.http.nio.protocol.HttpAsyncRequester.execute(HttpAsyncRequester.java:231)* * at lk.uom.test.transport.http.nio.AbstractNIOHttpSender.send(AbstractNIOHttpSender.java:319)* * at lk.uom.test.transport.http.nio.AbstractNIOHttpSender.send(AbstractNIOHttpSender.java:64)* * ....* Thanks, Sudheera. On Tue, Feb 28, 2017 at 3:15 PM, Oleg Kalnichevski <ol...@apache.org> wrote: > On Mon, 2017-02-27 at 23:38 +0530, Sudheera Palihakkara wrote: > > Hi all, > > > > I have recently upgraded from httpcore-nio 4.4 to 4.4.6 and when the > > load > > is quite high with high concurrency, for only a few invocations of > > HttpAsyncRequester.execute() the cancelled method is getting called > > of > > provided implementation of FutureCallback. I didn't get this issue > > with 4.4 > > any possible reasons or anything that i've missed during the upgrade. > > > > Thanks you. > > > > It is possible but there is not enough information about the problem to > be able to make any definitive statement. Please consider reproducing > the problem with a test application (preferably self-contained). > > Oleg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > > -- *Sudheera Palihakkara.* Undergraduate Department of *Computer Science and Engineering,*Faculty of Engineering, *University of Moratuwa*, Sri Lanka.
