Yes, the 'mode' of 'realms' and 'users' caches were changed to
'ASYNC'.
This causes the app to store the invalidations temporarily w/o sending to
other nodes and flush them all only when a threshold value is arrived. I
think this storage method causes the Serialization issue.
On Mon, Nov 30, 2015 at 7:30 PM, Bill Burke <bburke(a)redhat.com> wrote:
Did you change caching configuration?
On 11/30/2015 8:50 AM, Lohitha Chiranjeewa wrote:
> Issue came up with Realm and User caches. Not User Sessions.
>
> On Mon, Nov 30, 2015 at 7:17 PM, Bill Burke <bburke(a)redhat.com
> <mailto:bburke@redhat.com>> wrote:
>
> Or is this related to UserSession cache?
>
> On 11/30/2015 8:45 AM, Bill Burke wrote:
> > We don't replicate at all. Why would this be an issue?
> >
> > On 11/30/2015 8:41 AM, Lohitha Chiranjeewa wrote:
> >> When Infinispan caching is enabled in ASYNC mode, exceptions get
> logged
> >> at startup due to serialization issues. Basically the following
> classes
> >> have to implement the Serialiazable interface:
> >>
> >> org.keycloak.models.OTPPolicy
> >> org.keycloak.models.
> >> RequiredActionProviderModel
> >>
> >> There could be other classes as well.
> >>
> >> Is this already fixed in 1.7.0 code or shall I put a JIRA?
> >>
> >>
> >> Regards,
> >> Lohitha.
> >>
> >>
> >> _______________________________________________
> >> keycloak-user mailing list
> >> keycloak-user(a)lists.jboss.org <mailto:
> keycloak-user(a)lists.jboss.org>
> >>
https://lists.jboss.org/mailman/listinfo/keycloak-user
> >>
> >
>
> --
> Bill Burke
> JBoss, a division of Red Hat
>
http://bill.burkecentral.com
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org <mailto:keycloak-user@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>
>
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com