-
1. Re: infinispan question
pferraro Sep 9, 2011 10:39 AM (in response to lmcdasi)It looks like there's something screwy with the shared transport setup, which should be the default behavior (meaning, all stacks should share the same UDP layer by default). I'll look into this today.
In the meantime, can you try the following workaround? In the jgroups subsystem, add the following to the UDP transport:
<transport type="UDP" ... >
<property name="singleton_name">udp</property>
</transport>
-
2. Re: infinispan question
lmcdasi Sep 9, 2011 10:43 AM (in response to pferraro)Hi Paul,
Sorry - being busy with the other thread related to the services issue that I have. I can wait for the full fix on this one, unless the services issue gets addressed/solved faster or I there is a break on it ....
Also, any link that would help me understand inifinispan clustering on AS7 ? I am just seeing the 'tip of the iceberg' for now
Thanks!
BR,
Dan S.
-
3. Re: infinispan question
pferraro Sep 9, 2011 10:59 AM (in response to lmcdasi)I should have an initial draft of the "High-Availability Guide" finished today. Until then here are a couple resources:
(the section on clustering changes)
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7
http://infinispan.blogspot.com/2011/07/infinispan-in-jboss-as7.html
-
4. Re: infinispan question
pferraro Sep 9, 2011 11:00 AM (in response to lmcdasi)BTW - those log messages are annoying, but harmless.
-
-
6. Re: infinispan question
pferraro Sep 10, 2011 4:23 PM (in response to pferraro)OK - I found the issue. There's a bug in the jgroups subsystem that causes the 1st channel created for a given stack to not be configured using a shared transport, even though subsequent channels are. I'm submitting a pull request for this now.
-
7. Re: infinispan question
lmcdasi Sep 10, 2011 8:15 PM (in response to pferraro)Excellent ! Thank you for your help !
BR,
Dan S