WildFly Infinispan HTTP Session Replication Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
WildFly has built-in support to replicate/distribute session data amongst the cluster nodes, via the pre-configured cache container "web". | WildFly has built-in support to replicate/distribute session data amongst the cluster nodes, via the pre-configured cache container "web". | ||
| Line 28: | Line 25: | ||
</pre> | </pre> | ||
It is possible to use an external cache to cluster the session, see [[]] below. | It is possible to use an external cache to cluster the session, see [[#Using_JDG_as_External_Cache_Container_for_WildFly_HTTP_Session_Replication|Using JDG as External Cache Container for WildFly HTTP Session Replication]] below. | ||
=Using JDG as External Cache Container for WildFly HTTP Session Replication= | =Using JDG as External Cache Container for WildFly HTTP Session Replication= | ||
Revision as of 14:19, 1 June 2016
Internal
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.