HTTP Session Replication: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
The sever also must to be configured to support HTTP session clustering, see [[#WildFly_Server_Configuration|WildFly Server Configuration]] below. | The sever also must to be configured to support HTTP session clustering, see [[#WildFly_Server_Configuration|WildFly Server Configuration]] below. | ||
=WildFly-Specific Configuration= | |||
=WildFly Server Configuration= | =WildFly Server Configuration= | ||
Revision as of 16:12, 14 June 2016
Internal
Overview
The web application will be clustered if its web.xml contains the <distributable> tag:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<distributable/>
<!-- ... -->
</web-app>
From a server's perspective, <distributable> tells it to use a clustered session manager, which replicates (or distributes) sessions across the cluster, so all EAP nodes can have access to it. This way if a node fails, requests can be directed to other node, which still has access to the session state.
The sever also must to be configured to support HTTP session clustering, see WildFly Server Configuration below.