WildFly Infinispan HTTP Session Replication Configuration

Internal

• WildFly Infinispan Subsystem Configuration
• HTTP Session Replication

Overview

WildFly has built-in support to replicate/distribute session data amongst the cluster nodes, via the pre-configured cache container "web".

<subsystem xmlns="urn:jboss:domain:infinispan:1.5">
    ...
    <cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">
        <transport lock-timeout="60000"/>
        <replicated-cache name="repl" mode="ASYNC" batching="true">
            <file-store/>
        </replicated-cache>
        <replicated-cache name="sso" mode="SYNC" batching="true"/>
        <distributed-cache name="dist" mode="ASYNC" batching="true" l1-lifespan="0">
            <file-store/>
        </distributed-cache>
    </cache-container>
   ...
</subsystem>

It is possible to use an external cache to cluster the session, see Using JDG as External Cache Container for WildFly HTTP Session Replication below.

HTTP Session-Specific Configuration Considerations

Eviction must not be configured on the HTTP session cache.

Expiration must not be configured on the HTTP session cache.

The web subsystem handles these aspects internally.

Using JDG as External Cache Container for WildFly HTTP Session Replication

Using JDG as External Cache Container for WildFly HTTP Session Replication