[keycloak-user] Upgrading Keycloak and Infinispan conflict

Marek Posolda mposolda at redhat.com
Tue May 22 03:20:03 EDT 2018


We don't support rolling upgrades. You need to stop all the nodes in 
cluster and then start them again with newer version. The content of 
caches will be cleared.

Marek

On 15/05/18 10:25, Federico Navarro Polo - Info.nl wrote:
> Hi,
>
> We are upgrading our Keycloak environment to the latest stable version, and we’ve found out a problem with Infinispan. Our setup is a standalone-ha with distributed cache.
>
> Apparently, there were breaking changes when going from Keycloak 3.1.0 to 3.2.0, since some classes and enums were removed from codebase. Those entities are still cached by Infinispan, so after upgrading Keycloak, on restart, a big amount of ClassNotFoundException or IllegalArgumentException due to these changes.
>
> Is there any way to cleanly transition without clearing the caches?
>
> Met vriendelijke groet,
>
> Federico Navarro
>
> backend developer
>
> federico at info.nl<mailto:federico at info.nl>  |  LinkedIn<https://www.linkedin.com/company/info-nl>  |  -<tel:+31205309161>
>
> info.nl<http://www.info.nl/>
>
> Sint Antoniesbreestraat 16  |  1011 HB Amsterdam  |  +31 (0)20 530 9100<tel:+31205309100>
>
>
> _______________________________________________
> 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