Closed fsainovich closed 2 years ago
I have been extracted the file from your latest image (and use in my image and works):
<?xml version="1.0" encoding="UTF-8"?>
<infinispan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:infinispan:config:11.0 http://www.infinispan.org/schemas/infinispan-config-11.0.xsd" xmlns="urn:infinispan:config:11.0">
<cache-container name="keycloak">
<transport lock-timeout="60000" stack="${env.KC_DB}-jdbc-ping-tcp"/>
<local-cache name="realms">
<encoding>
<key media-type="application/x-java-object"/>
<value media-type="application/x-java-object"/>
</encoding>
<memory max-count="10000"/>
</local-cache>
<local-cache name="users">
<encoding>
<key media-type="application/x-java-object"/>
<value media-type="application/x-java-object"/>
</encoding>
<memory max-count="10000"/>
</local-cache>
<distributed-cache name="sessions" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<distributed-cache name="authenticationSessions" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<distributed-cache name="offlineSessions" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<distributed-cache name="clientSessions" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<distributed-cache name="offlineClientSessions" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<distributed-cache name="loginFailures" owners="2">
<expiration lifespan="-1"/>
</distributed-cache>
<local-cache name="authorization">
<encoding>
<key media-type="application/x-java-object"/>
<value media-type="application/x-java-object"/>
</encoding>
<memory max-count="10000"/>
</local-cache>
<replicated-cache name="work">
<expiration lifespan="-1"/>
</replicated-cache>
<local-cache name="keys">
<encoding>
<key media-type="application/x-java-object"/>
<value media-type="application/x-java-object"/>
</encoding>
<expiration max-idle="3600000"/>
<memory max-count="1000"/>
</local-cache>
<distributed-cache name="actionTokens" owners="2">
<encoding>
<key media-type="application/x-java-object"/>
<value media-type="application/x-java-object"/>
</encoding>
<expiration max-idle="-1" lifespan="-1" interval="300000"/>
<memory max-count="-1"/>
</distributed-cache>
</cache-container>
Were you able to see the differences?
As far I as remember, I used the same cache-ispn-jdbc-ping.xml
file to build the latest
image.
So, the cache-ispn-jdbc-ping.xml
is supposed to identical in the pre-build image and the one present in the 19.0.2
folder.
I've just pulled the docker image ivanfranchin/keycloak-clustered:latest
and run its docker container.
After that, I docker exec
into it and checked the cache-ispn-jdbc-ping.xml
inside /opt/keycloak/conf/
folder.
I've compared the file in the docker container and the one in https://github.com/ivangfr/keycloak-clustered/blob/master/19.0.2/cache-ispn-jdbc-ping.xml, and they are identical.
Let me know if you've found some issue.
Best regards
Hi Ivan, I think that I downloaded a wrong file. After your reply, I have cloned all the repo and use folder 19.0.2 and all is OK. My mistake.
Thank you so much for your quickly reply.
Fernando.
Hi @fsainovich No problem! Thanks for the feedback!
When I use your prebuilt image (ivanfranchin/keycloak-clustered:latest) i get follow columns in JGROUPSPING table:
But if I try to built my own image with the cache-ispn-jdbc-ping.xml inside the 19.0.2 folder (https://github.com/ivangfr/keycloak-clustered/tree/master/19.0.2), i get the followns results:
The column "update" don't exist and bind_addr is not equal.
Could you share the same cache-ispn-jdbc-ping.xml used to generate latest image ?
My dockerfile: