hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPASYNC-122) CloseableHttpAsyncClient executed old versions of requests
Date Mon, 15 May 2017 18:27:04 GMT

    [ https://issues.apache.org/jira/browse/HTTPASYNC-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011049#comment-16011049

Oleg Kalnichevski commented on HTTPASYNC-122:

Please attach wire / context log of the session as described here:


> CloseableHttpAsyncClient executed old versions of requests
> ----------------------------------------------------------
>                 Key: HTTPASYNC-122
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-122
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.1.3
>            Reporter: Jordan Zimmerman
>            Priority: Blocker
> I hope I've misunderstood something otherwise this seems quite severe.
> I execute a bunch of requests of the form:
> {{/v1/kv/a/b/c?index=12&recurse=true}}
> Sometime later the index changes so that the requests are:
> {{/v1/kv/a/b/c?index=22&recurse=true}} (or whatever)
> However, my server keeps seeing the old request (with index=12). 
> The problem appears to have something to do with {{HttpAsyncRequestExecutor#requestReady}}.
The call to {{getHandler(conn)}} returns an object that has the old URI. It never seems to
get removed. Frankly, I really don't understand the code so I can't say for sure.
> I'll try to come up with a test case. But, I was hoping this might ring a bell or two
before I invest a lot of time. Please let me know.

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