WildFly Infinispan HTTP Session Replication Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
=External=
=Internal=
=Internal=


* [[WildFly_Infinispan_Subsystem_Configuration#Subjects|WildFly Infinispan Subsystem Configuration]]
* [[WildFly_Infinispan_Subsystem_Configuration#HTTP_Session_Replication_Cache|WildFly Infinispan Subsystem Configuration]]
* [[HTTP_Session_Replication#WildFly_Server_Configuration|HTTP Session Replication]]
* [[HTTP_Session_Replication#WildFly_Server_Configuration|HTTP Session Replication]]


=Overview=
=Overview=


=Using JDG as External Cache Container=
WildFly has built-in support to replicate/distribute session data amongst the cluster nodes, via the pre-configured cache container "web".
 
<pre>
<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>
</pre>
 
The default HTTP session replication cache, if not configured otherwise, is "web.repl".
 
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.
 
For more details on HTTP session replication configuration at application level, see:
 
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[HTTP_Session_Replication#cache-name|HTTP Session Replication - <tt>cache-name</tt>]]
 
:[[HTTP_Session_Replication#replication-mode|HTTP Session Replication - <tt>replication-mode</tt>]]
</blockquote>
 
=HTTP Session-Specific Cache Configuration Considerations=
 
[[Infinispan Eviction|Eviction]] must not be configured on the HTTP session cache.
 
[[Infinispan Expiration|Expiration]] must not be configured on the HTTP session cache.
 
The web subsystem handles these aspects internally.
 
The pre-configured "repl" and "sso" caches are there as an example, they're not needed.
 
=Using JDG as External Cache Container for WildFly HTTP Session Replication=
 
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[Using JDG as External Cache Container for WildFly HTTP Session Replication]]
</blockquote>
 
=TODO=


* 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
<font color=red>
* Why does “batch” added to the Infinispan configuration gets JDG-based HTTP session storage working?
</font>

Latest revision as of 21:05, 8 February 2017

External

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>

The default HTTP session replication cache, if not configured otherwise, is "web.repl".

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.

For more details on HTTP session replication configuration at application level, see:

HTTP Session Replication - cache-name
HTTP Session Replication - replication-mode

HTTP Session-Specific Cache 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.

The pre-configured "repl" and "sso" caches are there as an example, they're not needed.

Using JDG as External Cache Container for WildFly HTTP Session Replication

Using JDG as External Cache Container for WildFly HTTP Session Replication

TODO

  • Why does “batch” added to the Infinispan configuration gets JDG-based HTTP session storage working?

Retrieved from "https://kb.novaordis.com/index.php?title=WildFly_Infinispan_HTTP_Session_Replication_Configuration&oldid=16861"