Wildfly docs are wrong then :(
Maybe this? I'm just guessing. You know I'm just googling stuff and
looking at standalone-ha.xml, right?
<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
<channel name="ee" stack="tcp"/>
</channels>
On 2/27/17 10:59 AM, John D. Ament wrote:
That didn't work.
Message: WFLYCTL0197: Unexpected attribute 'stack' encountered
at org.jboss.as.controller.parsing.ParseUtils.unexpected
<subsystem xmlns="urn:jboss:domain:infinispan:4.0">
<cache-container name="keycloak"
jndi-name="infinispan/Keycloak">
<transport lock-timeout="60000" stack="tcp"/>
John
On Mon, Feb 27, 2017 at 10:30 AM Bill Burke <bburke(a)redhat.com
<mailto:bburke@redhat.com>> wrote:
https://docs.jboss.org/author/display/WFLY10/Infinispan+Subsystem
The only thing in keycloak that needs to leverage
clustering/JGroups is
our Infinispan cache for Keycloak SSO Sessions. I've never personally
tried to use a different JGRoups stack. I believe you can set the
"stack" attribute in the transport tag. Let me know if you get it
working. I"ll expand on our docs.
<subsystem xmlns="urn:jboss:domain:infinispan:4.0">
<cache-container name="keycloak"
jndi-name="infinispan/Keycloak">
<transport lock-timeout="60000"stack="tcp"/>
On 2/27/17 9:57 AM, John D. Ament wrote:
> Hi
>
> I was wondering, has Keycloak been tested using Wildfly 10.1 TCP
based
> Jgroups? I'm told that the TCP ports are lazy, and I'm never
seeing them
> come up. It looks like Keycloak doesn't have a war file, no
web.xml and as
> a result no distributable flag.
>
> John
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user