Distributed cache (Infinispan/tcpping) does not work as expected #12886

elronzo · 2022-07-04T08:19:03Z

elronzo
Jul 4, 2022

I am experiencing troubles configuring a three node tcpping setup. This is my ispn-cache-config:

`

<!-- custom stack goes into the jgroups element -->
<jgroups>
    <stack name="tcpping" extends="tcp">
        <TCPPING
            timeout="3000"
            initial_hosts="1.2.3.142[7800],1.2.3.143[7800],1.2.3.144[7800]"
            port_range="0"
            num_initial_members="3"
            stack.combine="REPLACE"
            stack.position="MPING"
            />
    </stack>
</jgroups>

<cache-container name="keycloak">
    <transport lock-timeout="60000" stack="tcpping"/>
    <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>

` Nodes 1 and 3 are finding each other. Node 2 is not found and does not find the other cluster members.

Is my cache config correct?

Navigation Menu

Repository navigation

Distributed cache (Infinispan/tcpping) does not work as expected #12886

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Distributed cache (Infinispan/tcpping) does not work as expected #12886

Uh oh!

elronzo Jul 4, 2022

Replies: 0 comments

elronzo
Jul 4, 2022