https://issues.apache.org/bugzilla/show_bug.cgi?id=56828
--- Comment #2 from Filip Hanik <fha...@apache.org> --- faulty member is tcp://10.160.40.12:4444 is this member not responding to anything? now there are ways around this, such as configuring replication to be async. What happens then is that healthy nodes will keep responding to HTTP requests instead of waiting for faulty nodes. But it will mask faulty nodes. Your scenario here, could be that 10.160.40.12:4444 is experiencing another problem, such as an out of memory error or other serious problem. check for other log errors and the health of the instance itself. async message delivery is channelSendOptions=8 (fire and forget) channelSendOptions=10 (wait for an ack or resend) see http://tomcat.apache.org/tomcat-7.0-doc/config/cluster.html -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
