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 37896] - FastAsyncSocketSender blocks all threads on socket error
Date Thu, 15 Dec 2005 00:23:59 GMT
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 rainer.jung@kippdata.de  2005-12-15 01:23 -------
Fast async has been designed to be used asynchronously. With such a
configuration, no tcp communication for replication will be done during the
request-response lifecycle. Instead all replication messages will only put into
a local queue. Seperate threads will pick up these messages an send them. The
queue will be locked while taking out the messages, but the lock will b freed
before actually trying to send a message.

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


Mime
View raw message