tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4975] - Connection closed before response is sent
Date Thu, 17 Jan 2002 04:05:05 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4975>.
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

Larry.Isaacs@sas.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From Larry.Isaacs@sas.com  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:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message