You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/12/25 14:08:19 UTC

DO NOT REPLY [Bug 39600] - A lot of connection in TIME_WAIT state on Tomcat clients

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39600>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39600


yoavs@computer.org changed:

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




------- Additional Comments From yoavs@computer.org  2006-12-25 05:08 -------
While we can add the shutdownOutput call right before socket.close, I largely
agree with Darryl's analysis so I hesitate to muck with this low-level
functionality that's been seriously tested over several years now, at least not
without further tests / information from the original poster.

OP: if your problem persists with 5.5.20, could you please try adding the
shutdownOutput call to Http11BaseProtocol as Darryl suggests, building a custom
Tomcat, and re-running your tests?  I'd be very curious as to the results.  If
you do this, please reopen this Bugzilla issue and append your further
information.  Thanks.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org