We are still experiencing this problem.
To summarize:
1) We are using 6.0.18.
2) A single Tomcat works fine and joins the cluster.
3) Two Tomcats on the SAME MACHINE (different ports - duh) but
multicasting to DIFFERENT multicast IPs each join their respective
clusters. (yes, two clusters.)
4) Two Tomcats on the SAME machine multicasting to the SAME multicast
IP and we get "An operation was attempted on something that is not a
socket" when we launch the second tomcat.
5) The exact setup works fine on RHEL and Mac OS X
This is NOT the 6.0.20 regression (https://issues.apache.org/bugzilla/show_bug.cgi?id=47308
) – we're using 6.0.18.
This is NOT an issue with Windows getting confused by the bind
attribute – it works fine in cases 2 & 3 above.
Could it be that windows won't allow two apps to multicast to the same
address at the same time?
Can anyone help with this issue?
--johnt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
