Bela:
Thanks for looking into the issue. I thought that this must be as per design. The way
we use jgroups is that we have a protocol stack created and deployed with multiple
versions of our software. We cannot expect clients to configure jgroups ports, etc
when they deploy our app as our app
Can you send me ([EMAIL PROTECTED]) your patch ? I'll see whether this is a bug and,
if so, apply the patch. I have actually tested this against different versions of
JGroups, and it worked, so I'm a bit astonished that this would not be caught by the
version check.
Regards,
Bela
View the
Okay, this is as designed: someone should be able to use different versions of JGroups
if they know that the versions will work with each other. Therefore I just log a
warning, and *don't* discard the message.
Choose a different mcast address or port if you want to avoid these warnings.
Bela
