Re: [keycloak-user] Infinispan state transfer timeout on startup + Serialization exception on the other node
We're waiting for an update to WildFly that includes a new Infinispan
release to get this fixed. In the mean time, depending on how many nodes
you have, yes using a replicated cache will work.
On 8 November 2016 at 21:23, Gabriel Lavoie <glavoie(a)gmail.com> wrote:
Hi Stian,
during load/crash tests, we've encountered a few times the Infinispan
error described in the following ticket when restarting the "failed" node:
https://issues.jboss.org/browse/JBEAP-6002
As this would require an Infinispan update, do you think changing the
distributed cache to replicated caches could be an acceptable/tested
workaround?
Thanks!
Gabriel
--
Gabriel Lavoie
glavoie(a)gmail.com