-
1. Re: Modeshape in Replication with jgroups-tcp
hchiorean Dec 31, 2014 3:48 AM (in response to yawarabbas)1 of 1 people found this helpfulFrom your description this seems to be related to some JGroups/ISPN configuration peculiarities (possibly a bug - see this similar issue: [ISPN-2056] exception in stopping a component resulted in failing to stop cache manager - JBoss Issue Tracker)
Please post/cross-post this question on the Infinispan forums. Also, it would help to have the full stack trace & DEBUG logging enabled for JGroups
-
2. Re: Modeshape (infinispan) in Replication with jgroups-tcp
yawarabbas Dec 31, 2014 5:26 AM (in response to hchiorean)Thanks Horia Chiorean,
I moved the discussion in Infinispan forum. My purpose was to know any other way around to achieve the replication (if possible by modeshape). But it seems that only the infinispan manages this replication/clustering with jgroups-tcp.
And i think i am missing something (probably any service etc) at remote machineB, to listen for jgroup-tcp requests from machineA. Plz correct me if i am wrong or any guideline to register/install that receiving end service/configuration. Thanks
-
3. Re: Modeshape (infinispan) in Replication with jgroups-tcp
hchiorean Dec 31, 2014 6:21 AM (in response to yawarabbas)1 of 1 people found this helpfulMy purpose was to know any other way around to achieve the replication (if possible by modeshape). But it seems that only the infinispan manages this replication/clustering with jgroups-tcp.
That is correct. ModeShape does not implement any clustering behavior by itself really. Instead, it relies on the configuration of Infinispan & JGroups.
-
4. Re: Modeshape (infinispan) in Replication with jgroups-tcp
yawarabbas Dec 31, 2014 11:48 AM (in response to yawarabbas)Much Thanks for the cooperation.
Finally the issue found in my jgroups-tcp configuration. It is resolved when I entered the bind_addr of the same machine (where the application instance was hosted) in tcp configuration. And entered the comma separated list of all remote hosts in TCPPING initial_hosts as follows:
<TCPPING timeout="3000"
initial_hosts="192.168.30.25[7800],192.168.30.27[7800]"
port_range="5"
num_initial_members="2"
ergonomics="false" />