New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
org.infinispan.commons.CacheException:java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.ClassDescriptors #19739
Comments
OK so, downgrading java from 17 to 11 "fixed" it. |
@Stono Thanks for to report. This seems to be a problem in Infinispan/jboss-marshalling. I created https://issues.redhat.com/browse/ISPN-14824 |
It seems a target release with the fix is Infinispan 14.0.10.Final infinispan/infinispan#10890 |
Infinispan upgrade to 14.0.10.Final is now merged in |
@taha-upstart I'm not sure. I recall some changes related to ISPN 14 upgrade. Some changes were related just to testsuite. I guess you need to try it to be 100% sure. |
@martin-kanis keycloak v22.0 release notes mention inifinispan upgrade to v14.0.8 which doesn't fix the reported bug here. is infinispan v14.0.10 planned to be released with 22.0.2? |
@taha-upstart 22.0.1 contains Infinispan 14.0.10 https://github.com/keycloak/keycloak/blob/22.0.1/pom.xml#L80 EDIT: Keycloak 22.0.0 is also Infinispan 14.0.10 https://github.com/keycloak/keycloak/blob/22.0.0/pom.xml#L80. If that is not working for you, maybe the problem wasn't fixed properly. |
perfect! thanks @martin-kanis . I was confused since the 22.0.1 release notes did not mention anything about that! https://www.keycloak.org/2023/07/keycloak-2201-released.html |
Before reporting an issue
Area
infinispan
Describe the bug
Hi,
I'm currently doing a 20->21 upgrade, and in doing so have also bumped the java version from 11 to 17 due to Java 11 support being deprecated.
I run on kubernetes, with
KC_CACHE_STACK
=kubernetes
.I noticed after the upgrade that if I go to the admin UI, and click
sessions
I get an error:Network response was not OK.
. Looking at the network request, we got a 500 back from the keycloak server.There is a corresponding error log at the bottom of this issue.
Now the really strange thing; this only happens when I have
3
replicas of keycloak running. When I scale down to2
or1
, then there is no error. I had a theory it was something to do with the default cacheowners="2"
, eg when running with 3 replicas perhaps it was hitting the node which wasn't an owner. I attempted to create a customcache-ispn.xml
setting that to 3, but it had no effect.Not really sure where to go from here!
Version
21.0.2
Expected behavior
Sessions to work
Actual behavior
Sessions don't work :D
How to Reproduce?
Run 21.0.2 on kubernetes with 3 replicas, using
KC_CACHE_STACK=kubernetes
.Anything else?
No response
The text was updated successfully, but these errors were encountered: