On 7/11/11 5:32 PM, peterjca wrote:
> The standard client works as well now.
thanks, good to know
> I disagree that it's not a bug. If you don't read all responses then, as far
> as my app was concerned, the side-effect was catastrophic.
>
> Why should a completely separate resource end up getting duplicate posts
> that have already been received and processed by it before, simply because
> you have failed to read the response from another resource? *What causes
> that?* That is a very nasty side-effect, and really really really sounds
> like a bug to me.... ...unless you can explain what is going on and why and
> where this is documented in the User Guide?
true, that is a bug BUT not in jersey client workspace, but probably in
HttpURLConnection class (I'm sure that the other request is not done by
jersey client, it is just repeated by lower layer, which (as you state)
surely is a bug). We recently investigated this behavior with Oleksiy
and we confirmed that second request is sometimes made (when response
InputStream is not properly closed).
My point in the previous email was that we can't do anything about it
from "jersey" layer, issue is somewhere deeper, in this case most likely
in HttpURLConnection (part of JDK) but you can prevent it by closing
returned InputStream.
Regards,
Pavel
>
> --
> View this message in context: http://jersey.576304.n2.nabble.com/Is-Jersey-Jersey-client-duplicating-requests-tp6570645p6571350.html
> Sent from the Jersey mailing list archive at Nabble.com.
>