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 2005/12/14 23:32:23 UTC

DO NOT REPLY [Bug 37896] - FastAsyncSocketSender blocks all threads on socket error

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=37896>.
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=37896





------- Additional Comments From tedman@sfu.ca  2005-12-14 23:32 -------
I'll try to get a copy of the new code, I'm not so sure I can test it though as
the circumstances are quite particular in reproducing this problem and I can't
really take down our live site to test it. I'll at least read through it to see
if the blocking scenerio can take place.

As for the node, yes I think so if I understand your question properly, we only
have 1 node name, and 1 domain name, and 1 context which is distributable.

-- 
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