A JUnit test case that we could patch into the HttpClient tests would be
ideal ...
As of yet, I haven't written any test cases for this problem.
Perhaps you can provide the stack trace of the exception failure, or a
more specific "trace" of the scenario, mentioning routine names (and
line numbers?) as I have attempted to do based on your description?
You might also consider including a "wire" level debug trace, and/or
snooping on the connection (see the mailing list archive for tips on
how you might do this). Maybe, you could augmenting
SimpleHttpConnection so that it can mimic the unexpected close for
you, and make your case 100% reproducible for others.
-Eric.
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
