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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] 2005-12-15 00:25 --- Okay I had a look at the new code and I'm pretty sure the problem will still manifest itself. The problem isn't with the code perse but I think it's a problem with the design of the replication. Since the replication is in-line with the HTTP request (seems like new session requests are inline even in asynch mode), if something bad happens to the replication socket which causes it to hang, it will block that thread (presumably until SO_TIMEOUT which is usually 2 minutes). If a subsequent request comes in for a new session, it will try to do the same thing but it needs to aquire a lock on the DataSender object via sendMessage(); therefore, this thread will now block until the previous thread timesout. As a result a lot of threads may backup while waiting for the original socket to timeout. Note that this could happen even in pooled mode, if all 300 threads had their own 300 replicator sockets, and each sat there waiting to timeout for 2 minutes, then there wuld be no more threads available (assuming I'm maxed at 300 threads). The only things I can really think of to resolve this is to have the replication on a separate thread to the http requests. Of course maybe I'm just mis-reading the code and everything I'm saying might be wrong... -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-12-15 08:57 --- Hmm, when you don't want update complete to 5.5.15 (svn head) you can compile the cluster module and copy the resulting catalina-cluster.jar inside 5.5.12 release. The default cluster configuration normaly used fastasyncqueue, the problem is that the subclass not implement the right method. Now is fixed and all is working well. 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
