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=39931>. 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=39931 Summary: Using mcastBindAddress for Tomcat Clustering fails to receive multicast packets Product: Tomcat 5 Version: 5.5.12 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Catalina:Cluster AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] With two systems, I tried to enable clustering so that sessions would replicate in case of a failure on one of the systems. The two systems have 3 network cards in them. eth2 goes to the NAS while eth1 and eth0 are on the main network of other apache and tomcat servers. eth0 is a backup for eth1 and is normally down. The problem seems to be when I specify which interface to bind to in the Membership node of server.xml. If I specify mcastBindAddress="<eth1-ip-address>", I can tell that Tomcat is listening and sending on this address. However, it seems that packets never get delivered to the receive method in the McastServiceImpl class. I've confirmed that the multicast traffic reaches the machine but with debug logging on, I never get the 'mcast receive' log message. If I remove the mcastBindAddress attribute from the Membership node in server.xml, the multicast traffic gets delivered and session replication works. On single-homed systems, it does not seem to matter if mcastBindAddress is set or not - the multicast packets get delivered. -- 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]
