On Wed, 2011-03-30 at 16:17 -0500, Vadheraju, Rajeshwar wrote: > Thanks, Oleg. > If I implement "retry", It may resolve #1 of 3 issues that I have. > Again, I was running into > 1) Connection Reset - Client is trying write/send a request, connection > broken - "retry" perfectly work > 2) Broken Pipe - Client is trying to read the response from server, > connection broken. In this situation, If I "retry", I see HttpClient retries > entire request, which could cause server to receive duplicate requests, which > is not desirable. > 3) Server failed to respond error - NoHttpResponseException - I think it is > similar to #2 above. >
HTTP was _never_ intended or designed for use in transactional systems. Systems that use HTTP as a transport mechanism must either be prepared to live with the fact that some messages may get lost in transit or deal with the fact that some messages may get submitted multiple times. The most pragmatic approach to solving the problem I know of is passing a UID of some sort with each and every non-idempotent HTTP request. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
