[keycloak-user] Query on high availability- HA of Keycloak docker

Sebastian Laskawiec slaskawi at redhat.com
Mon Aug 26 05:15:30 EDT 2019


Perhaps you might be interested in Docker Compose example that is currently
under review: https://github.com/jboss-dockerfiles/keycloak/pull/204

On Sun, Aug 25, 2019 at 9:10 PM vijay <vijaybaliyan at gmail.com> wrote:

> Hi All,
>
> For development my setup has two keycloak containers on single VM along
> with postgres sql.  I am following the document mentioned
> https://github.com/jboss-dockerfiles/keycloak/tree/master/server .
> I am starting the keycloak and keycloak2 docker containers with
>
>
> docker run -p 8080:8080 --name keycloak --link postgres:postgres -e
> JGROUPS_DISCOVERY_PROTOCOL=JDBC_PING -e POSTGRES_DATABASE=keycloak -e
> POSTGRES_USER=keycloak -e POSTGRES_PASSWORD=password -v
> $HOME/docker/volumes/keycloak:/tmp -d jboss/keycloak
>
> docker run -p 8081:8080 --name keycloak2 --link postgres:postgres -e
> JGROUPS_DISCOVERY_PROTOCOL=JDBC_PING -e POSTGRES_DATABASE=keycloak -e
> POSTGRES_USER=keycloak -e POSTGRES_PASSWORD=password -v
> $HOME/docker/volumes/keycloak2:/tmp -d jboss/keycloak
>
> In the server logs of both keycloak containers I see below error logs -
>
> 19:02:01,596 WARN  [org.jboss.as.dependency.private] (MSC service thread
> 1-1) WFLYSRV0018: Deployment "deployment.keycloak-server.war" is using a
> private module ("org.kie") which may be changed or removed in future
> versions without notice.
> 19:02:02,181 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool
> -- 60) MSC000001: Failed to start service
> org.wildfly.clustering.jgroups.channel.ee:
> org.jboss.msc.service.StartException in service
> org.wildfly.clustering.jgroups.channel.ee:
> java.lang.IllegalStateException:
> java.lang.IllegalArgumentException: Either the 4 configuration properties
> starting with 'connection_' or the datasource_jndi_name must be set
>         at
>
> org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70)
>         at
>
> org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117)
>         at
>
> org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
>         at
>
> org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
>         at
>
> org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
>         at
>
> org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
>         at java.lang.Thread.run(Thread.java:748)
>         at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.IllegalStateException:
> java.lang.IllegalArgumentException: Either the 4 configuration properties
> starting with 'connection_' or the datasource_jndi_name must be set
>         at
>
> org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116)
>         at
>
> org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58)
>         at
>
> org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67)
>         ... 7 more
> Caused by: java.lang.IllegalArgumentException: Either the 4 configuration
> properties starting with 'connection_' or the datasource_jndi_name must be
> set
>         at
>
> org.jgroups.protocols.JDBC_PING.verifyConfigurationParameters(JDBC_PING.java:421)
>         at org.jgroups.protocols.JDBC_PING.init(JDBC_PING.java:102)
>         at
> org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:847)
>         at org.jgroups.stack.ProtocolStack.init(ProtocolStack.java:837)
>         at org.jgroups.JChannel.<init>(JChannel.java:200)
>         at
>
> org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:116)
>         at
>
> org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96)
>         ... 9 more
>
>
> Any hint will be helpful.
>
> Thanks,
> Vijay
> _______________________________________________
> 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