Jordan Zimmerman created HTTPASYNC-122:
------------------------------------------
Summary: 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
