hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yaping liu (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (HTTPASYNC-36) SocketTimeoutException can result in failed() being called multiple times
Date Fri, 06 Jun 2014 18:42:02 GMT

     [ https://issues.apache.org/jira/browse/HTTPASYNC-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

yaping liu updated HTTPASYNC-36:

    Comment: was deleted

(was:   I'm using 4.0 GA, and having issues happening @BaseIOReactor:sessionTimedOut, actually
my request just got in a couple of milliseconds, and it's got timed out where my socket timeout
is set to 10 seconds, so this immature SocketTimeoutException is throwing out. I feel that
there is a race condition, can it when it's returning the connection from the pool and when
the selector is iterating the keyset? because of this issue, we are hesitant to move to HttpAsyncClient


> SocketTimeoutException can result in failed() being called multiple times
> -------------------------------------------------------------------------
>                 Key: HTTPASYNC-36
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-36
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.0-beta3
>            Reporter: Clinton Nielsen
> Appears to be a race condition, so I am having trouble duplicating, but we have observed
the failed callback method being called twice for a single request that timed out.
> Following stack trace was logged twice for a single request:
> HttpAsyncRequestExecutor.java:279:org.apache.http.nio.protocol.HttpAsyncRequestExecutor:timeout
> LoggingAsyncRequestExecutor.java:128:org.apache.http.impl.nio.client.LoggingAsyncRequestExecutor:timeout
> DefaultHttpClientIODispatch.java:136:org.apache.http.impl.nio.DefaultHttpClientIODispatch:onTimeout
> DefaultHttpClientIODispatch.java:50:org.apache.http.impl.nio.DefaultHttpClientIODispatch:onTimeout
> AbstractIODispatch.java:169:org.apache.http.impl.nio.reactor.AbstractIODispatch:timeout
> BaseIOReactor.java:257:org.apache.http.impl.nio.reactor.BaseIOReactor:sessionTimedOut
> AbstractIOReactor.java:494:org.apache.http.impl.nio.reactor.AbstractIOReactor:timeoutCheck
> BaseIOReactor.java:207:org.apache.http.impl.nio.reactor.BaseIOReactor:validate
> AbstractIOReactor.java:284:org.apache.http.impl.nio.reactor.AbstractIOReactor:execute
> BaseIOReactor.java:106:org.apache.http.impl.nio.reactor.BaseIOReactor:execute
> AbstractMultiworkerIOReactor.java:604:org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker:run
> Thread.java:636:java.lang.Thread:run | class java.net.SocketTimeoutException

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message