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 Wed, 14 Dec 2005 07:32:12 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


pr@objektpark.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From pr@objektpark.de  2005-12-14 08:32 -------
Update to the current svn head.
I have fixed a DataSender refactoring bug. This means that tomcat 5.5.12 cluster
send all messages thread synchronized with only one sender socket. 
Other bug is that the membership message format has changed (s. Bug 37808)

Can you please test with the newest cluster code?

I reference your report now at changelog.
I am not sure that your szenarion not show another problem!

Is it true, that all your nodes are inside the same cluster replication domain?

Sorry for the trouble and thanks for analyse and reporting the bug
Peter

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