Summary: | When mcastBindAddress is set and disabling/enabling interface on Win get infinite NoRouteToHostException | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | David Gagnon <dgagnon> |
Component: | Catalina:Cluster | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | P2 | ||
Version: | 5.5.16 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
David Gagnon
2006-07-14 00:36:13 UTC
When you enable the route again, does it correct itself, or do you require a tomcat restart. I have a feeling that code needs to better self heal itself, but wanted to get your input first. Filip I've added a fix to Tomcat 6.0 and 6.x (in trunk). Basically, it does attempt a recovery after such a failure. There are still a few issues to work through, one of them being, what should be done to the existing membership, since we are not receiving mcast packets due to a local error, then is it really appropriate to expire members? I have backport the Filips fix from tomcat 6.0.x. It works for me at my MAC's, but I am not sure that it also work with other OS's. Feedback is very welcome Peter - At my mac (jdk 1.5.0_07) I see some SocketTimeoutException and IOException after send is going wrong. After four failures the kernel create a new multicast route! Strange... After interface is back the old route is recreated. No feedback so assume Peter's backport did indeed work. |