[keycloak-user] Infinispan state transfer timeout on startup + Serialization exception on the other node

Bill Burke bburke at redhat.com
Wed Nov 9 08:34:46 EST 2016

Is this going to be reflected in product?  If not, we can't really 
depend on any new Infinispan interface and have to go with the Wildfly 
version product is based on, IMO.

On 11/9/16 1:52 AM, Stian Thorgersen wrote:
> 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 at 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 at gmail.com
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user

More information about the keycloak-user mailing list