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=42689>. 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=42689 Summary: no way to timeout new connect attempts for replication sockets Product: Tomcat 5 Version: 5.5.23 Platform: Sun OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Catalina:Cluster AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While testing clustering in our lab we noticed that when connectivity to one of the cluster members was lost by pulling the network cable (serving replication traffic), the entire cluster would become unresponsive. We were pulling the network cable to simulate catastrophic switch port failure or interface failure. We were testing under load, using synchronous replication. We found that existing replication sockets would honor our timeout (ackTimeout) configurations, but new connections established because of pool growth or retries would not timeout socket connect attempts. Because of not having a timeout, requests would backlog and effectively bring the cluster down. Theoretically, this connection establishment problem exists for all users of the DataSender class. -- 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]