From what Stelios is telling me the question is a little bit other way round: he is using library mode infinispan and jgroups in EAP and connecting to JDG. So the question is what JDG is doing with the stack, not AS/WF as its infinispan/jgroups subsystem is not used.
Unfortunately I don't have access to the JDG repo so I don't know what changes have been made there but if you are using the same jgroups logic, IMO the channel needs to be wrapped as org.jboss.as.clustering.jgroups.MuxChannel before passing to infinispan. Rado On 26/09/14 15:03, Galder Zamarreño wrote: > Hey Paul, > > In the last couple of days, a couple of people have encountered the exception > in [1] when trying to cluster a standalone Infinispan app with its own > JGroups configuration file with a AS/WF running Infinispan cache. > > From my POV, 3 possible causes: > > 1. Dependency mismatches between AS/WF and the standalone app. Having done > some quick study of Kurt’s case, apart from micro version changes, all looks > good. > > 2. Mismatch in the Infinispan and/or JGroups configuration file. > > 3. AS/WF puts something on the clustered wire that standalone Infinispan does > not expect. Are you still doing multiplexing? Could you be adding extra info > to the wire? > > With this email, I’m trying to get some clarification from you if the issue > could be due to 3rd option. If it’s either of the first two, it’s a matter of > digging and finding the difference, but if it’s 3rd one, it’s more > problematic. > > Any ideas? > > [1] https://gist.github.com/skoussou/92f062f2d0bd17168e01 > -- > Galder Zamarreño > [email protected] > twitter.com/galderz > _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
