Hmm, it supposed to be thread-safe if used properly.
Now it's either bug or just improper use.
I agree with your observation regarding 302 processing and that the
payload shouldn't be re-sent (it's something I have to take a look at),
but not sure I remember the testcase, that confirms, that
FeedableBodyGenerator is not thread-safe.
Thanks.
WBR,
Alexey.
On 05.06.15 15:47, testn wrote:
> Alexey,
>
> Since the existing code in Jersey/AHC uses FeedableBodyGenerator in a
> non-thread-safe way. What is your recommendation to address the problem?
>
>
>
> --
> View this message in context: http://grizzly.1045725.n5.nabble.com/Grizzly-http-client-race-condition-tp5710847p5710875.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.