-
|
Hi, I'm trying to upgrade to Keycloak 22.0.0 and version 21.1.2 works fine on my Digital Ocean platform. However, it is using Infinispan 14.0.9.Final. As soon as I try to use 14.0.10 I get the JGroups channel error below. Looking at the release notes I am not sure what changed between these versions, but the code that causes the issue is in Is there any way to resolve this and get Keycloak upgraded?
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 10 replies
-
|
The main cause seems to be |
Beta Was this translation helpful? Give feedback.
-
|
@tristantarrant Sorry for the late reply. It is running on Digital Ocean's App Platform so I don't have access to the networking, best I could do is get the IP from the host, but one is the CDN address: 172.66.0.96 I have not touched the JGroups config, just using the docker image from quay.io, so it should be the default. It works fine and starts Keycloak with Keycloak 21.1.2 but 22.0.0+ throws this JGroups error. It is for sure a multicast issue as I don't think multicast is supported on Digital Ocean, but I'm not sure how I can disable this. |
Beta Was this translation helpful? Give feedback.
-
|
I imagine this is a limitation of Digital Ocean, as I know AWS, GCP, and Azure all support multicast. It seems the only option here @tristantarrant is to stick to Infinispan 14.0.9 if the app needs to run on DO. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think this is true: most cloud platforms don't support IP multicasting. You could try setting UDP(ip_mcast="false"), but then I'd recommend switching to TCP anyway if you do that. |
Beta Was this translation helpful? Give feedback.
-
|
The fact is that nothing has changed wrt multicast in 14.0.10.
You can however configure jgroups to use other transports and discoveries,
such as TCP
…On Tue, 12 Sept 2023, 22:52 iconitech, ***@***.***> wrote:
I imagine this is a limitation of Digital Ocean, as I know AWS, GCP, and
Azure all support multicast. It seems the only option here @tristantarrant
<https://github.com/tristantarrant> is to stick to Infinispan 14.0.9 if
the app needs to run on DO.
—
Reply to this email directly, view it on GitHub
<#11285 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC72HRIMZN7S2CLT6IRP4TX2DDRZANCNFSM6AAAAAA4UMF6ZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I think this is caused by a change in the JGroups configuration shipped by Keycloak, since nothing changed between 14.0.9 and 14.0.10. Maybe @ahus1 can help here. |
Beta Was this translation helpful? Give feedback.
-
|
@iconitech - The error message "No such device" points to something very deep down in the network stack. Keycloak 22.0.0 switched to IPv4+IPv6 dualstack support by default. See https://www.keycloak.org/docs/22.0.0/upgrading/#keycloak-supports-ipv4ipv6-dual-stack for the migration guide. Follow the link to the configuration guide to disable IPv6 to restore the original behavior. Maybe this will help in your setup - please let me know if this fixes it for you. |
Beta Was this translation helpful? Give feedback.
-
|
Simple test: run with |
Beta Was this translation helpful? Give feedback.
-
|
Sorry guys, indeed I guess it was not an Infinispan issue but the way Keycloak uses JGroups in versions 22.0.0+. I was able to fix it by adding However, now I'm wondering how Keycloak works by default on cloud environments since most don't allow multicast. Thanks for all the suggestions! |
Beta Was this translation helpful? Give feedback.
-
|
@iconitech - setting Please use the documentation on https://www.keycloak.org/server/caching to find out a cache stack that works for you. It also links to the Infinispan documentation where you can find more details on the cache stacks. |
Beta Was this translation helpful? Give feedback.
-
|
@ahus1 Thanks, it is a very basic 1 instance Keycloak on Digital Ocean's App platform, so I do not need distributed caching. But I think Keycloak changed the default for having distributed caching enabled from false to true in their newer versions, which I guess caused an issue for very basic installations. |
Beta Was this translation helpful? Give feedback.
Sorry guys, indeed I guess it was not an Infinispan issue but the way Keycloak uses JGroups in versions 22.0.0+. I was able to fix it by adding
--cache=local --cache-stack=tcpto the build.However, now I'm wondering how Keycloak works by default on cloud environments since most don't allow multicast.
Thanks for all the suggestions!