On 12/23/2009 01:46 PM, John Tangney wrote:
On Dec 23, 2009, at 12:19 PM, Filip Hanik - Dev Lists wrote:
On 12/23/2009 11:42 AM, John Tangney wrote:
it's failing on this operation:
socket.setInterface(mcastBindAddress);
There is a small chance that Window's doesn't allow multicast
sockets to be bound to an IP
try removing the "bind" attribute
No, that can't be it
did you try it?
Yes, I did try that.
With the bind attribute, a SINGLE tomcat binds to the correct NIC and
the cluster works perfectly. It's only when we have TWO tomcats both
on the same machine that we have the problem.
That, my friend, is a totally different problem. A regression in in
6.0.20 only
https://issues.apache.org/bugzilla/show_bug.cgi?id=47308
Will be fixed in the next release
Filip
Without the bind attribute, Tomcat binds to the wrong NIC which
prevents the other nodes from getting the multicast packets.
I could experiment with another windows box to see if I can run 2
tomcats without the bind attribute. (I can't do that on the machine
that's experiencing the prob because it's a production box.) But even
if that works, we stuck, because we have to use the 2nd NIC for
clustering.
Could it be that a socket is not being closed?
Thanks!
--johnt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
