Using JDG as External Cache Container for WildFly HTTP Session Replication

External

• Externalizing Sessions with JDG https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.6/html/Administration_and_Configuration_Guide/chap-Externalize_Sessions.html

Internal

• WildFly Infinispan HTTP Session Replication Configuration

Overview

JDG can be used as an external cache container for HTTP session data within WildFly. This allows scaling of the data layer independent of the application, and enables different WildFly clusters, that may reside in various domains, to access data from the same JDG cluster.

Setup the JDG Cluster

Configuration details are available here: Infinispan Configuration. The external JDG cluster will be accessed by the WildFly instance over the HotRod protocol.

Define a dedicated cache for each web application In this specific case, the dedicated cache name is "http-sessions":

<subsystem xmlns="urn:infinispan:server:core:6.4">
  <cache-container name="clustered" default-cache="default" statistics="true">
    <transport executor="infinispan-transport" lock-timeout="60000"/>
    <distributed-cache name="default" ...>
      ...
    </distributed-cache>
    <distributed-cache name="http-sessions" owners="2" mode="SYNC" start="EAGER"/>
  </cache-container>
  ...
</subsystem>