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
have come across a bug related to version
compatibility. We are using jgroups with jboss-cache.
We recently upgraded to version 2.2.3. However there
are still some machines on our network with an old jgroups
version - 2.2.0. Multicasting between these machines
throws the following error.
-
