This sounds like it is the opposite problem. Your connection is probably being closed for you somehow after being idle.
Depending on your speed requirements, you can re-open the transport for each burst of activity or you can use a pooling strategy to close idle connections and re-open them when you need to do more work. On Wed, May 6, 2009 at 4:16 PM, Curtis Spencer <[email protected]> wrote: > Also, one other thing I ought to mention is that I have never seen it > happen when the service is under a heavy load. Usually when a first > request after a lull period or after a deploy. >
