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 > https://lists.jboss.org/mailman/listinfo/keycloak-user >

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@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

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&gt; 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&gt; >> >> 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 > _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user

I agree that there could be inconsistent behavior with ASYNC mode depending on what your use case is. However, shouldn't the classes I mentioned be made serializable in any case? They are directly referenced from the classes inside infinispan cache model package. On Nov 30, 2015 7:56 PM, "Stian Thorgersen" <sthorger(a)redhat.com&gt; wrote: > I wouldn't not recommend setting async as you may get unpredictable > behavior > > On 30 November 2015 at 15:07, Lohitha Chiranjeewa <kalc04(a)gmail.com&gt; > wrote: > >> 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&gt; 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&gt; >>>> >> 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(a)lists.jboss.org&gt; >>>> 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 >> https://lists.jboss.org/mailman/listinfo/keycloak-user >> > >

Been digging into this some more and turns out there's a pretty nasty bug [1] in the way we our caches are implemented. It's a simple fix though and will be resolved for 1.7. [1] https://issues.jboss.org/browse/KEYCLOAK-2179 On 1 December 2015 at 10:40, Stian Thorgersen <sthorger(a)redhat.com&gt; wrote: > We can make those classes serializable. Create a JIRA for it. It's to > late for 1.7 release though so won't be fixed until 1.8. > > We also don't do any testing with ASYNC (as we know it will be > problematic, especially since Keycloak doesn't require sticky sessions) or > replicated caches, as we recommend using sync + invalidation caches. > > On 30 November 2015 at 17:56, Lohitha Chiranjeewa <kalc04(a)gmail.com&gt; > wrote: > >> I agree that there could be inconsistent behavior with ASYNC mode >> depending on what your use case is. >> >> However, shouldn't the classes I mentioned be made serializable in any >> case? They are directly referenced from the classes inside infinispan cache >> model package. >> On Nov 30, 2015 7:56 PM, "Stian Thorgersen" <sthorger(a)redhat.com&gt; wrote: >> >>> I wouldn't not recommend setting async as you may get unpredictable >>> behavior >>> >>> On 30 November 2015 at 15:07, Lohitha Chiranjeewa <kalc04(a)gmail.com&gt; >>> wrote: >>> >>>> 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&gt; 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&gt; >>>>>> >> 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(a)lists.jboss.org&gt; >>>>>> 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 >>>> https://lists.jboss.org/mailman/listinfo/keycloak-user >>>> >>> >>> > _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user