DO NOT REPLY [Bug 4975] - Connection closed before response is sent

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4975

Connection closed before response is sent

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2003-08-26 06:06 ---
*** Bug 22588 has been marked as a duplicate of this bug. ***

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 4975] - Connection closed before response is sent

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4975

Connection closed before response is sent

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-01-16 20:05 ---
Jakarta Cactus was experiencing the same kind of problem when running on a high
powered Windows system.  I would be curious if in your situation, the client
was also on the same system.

The fix was to add a delaySocketClose attribute to the Http10Connector which
if set to "true", would add the Thread.yield() you are looking for.  The
default is currently "false".  This fix is present in the current nightly 3.3.1
build.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: