Chapter 17. HTTP session state replication
A dedicated software-based service designed to distribute HTTP client session requests across multiple computer servers (cluster). The primary directive of a software load balancer is to maximize resource utilization, reduce request response times, and prevent server overload. The load balancer forwards client session requests to a server cluster, based on server load and availability.
A semi-permanent connection between the client (an application) and the server. The load balancer determines whether the client session is created with persistence, or whether a client session is redistributed based on server load and availability.
Session persistence is a feature where information about a client's session is stored by the server so that if the client's connection is interrupted temporarily, the session can continue at the time the connection error occurred. A persistent session is also commonly known as a sticky session .
See Session Persistence.
17.1. Enabling session replication in your application
web.xmldescriptor. Here's an example:
<?xml version="1.0"?> <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>
replication-configelement in the
jboss-web.xmlfile. However, the
replication-configelement only needs to be set if one or more of the default values described below is unacceptable. All of the configuration elements are optional, and can be omitted if the default value is acceptable.
<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 5.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> <jboss-web> <replication-config> <cache-name>custom-session-cache</cache-name> <replication-trigger>SET</replication-trigger> <replication-granularity>ATTRIBUTE</replication-granularity> <replication-field-batch-mode>true</replication-field-batch-mode> <use-jk>false</use-jk> <max-unreplicated-interval>30</max-unreplicated-interval> <snapshot-mode>INSTANT</snapshot-mode> <snapshot-interval>1000</snapshot-interval> <session-notification-policy>com.example.CustomSessionNotificationPolicy</session-notification-policy> </replication-config> </jboss-web>
- element determines when the container should consider that session data must be replicated across the cluster. The rationale for this setting is that after a mutable object stored as a session attribute is accessed from the session, in the absence of a
setAttributecall, the container has no clear way to know if the object (and hence the session state) has been modified and needs to be replicated. This element has 3 valid values:SET_AND_GET is conservative but not optimal (performance-wise): it will always replicate session data even if its content has only been accessed and not modified. This setting made (a little) sense in JBoss Enterprise Application Platform 4 since using it was a way to ensure that every request triggered replication of the session's timestamp. Since setting
max_unreplicated_intervalto 0 accomplishes the same thing at much lower cost, using
SET_AND_GETmakes no sense with JBoss Enterprise Application Platform 5 or JBoss Enterprise Web Platform 5.SET_AND_NON_PRIMITIVE_GET is conservative but will only replicate if an object of a non-primitive type has been accessed (in effect, the object is not of a well-known immutable JDK type such as
String, etc.) This is the default value.SET assumes that the developer will explicitly call
setAttributeon the session if the data needs to be replicated. This setting prevents unnecessary replication and can have a major beneficial impact on performance, but requires very good coding practices to ensure
setAttributeis always called whenever a mutable object stored in the session is modified.In all cases, calling
setAttributemarks the session as needing replication.
- Specifies the name of the JBoss Cache configuration that should be used for storing distributable sessions and replicating them around the cluster. This element lets web applications that require different caching characteristics specify the use of separate, differently configured, JBoss Cache instances. In JBoss Enterprise Application Platform 4 the cache to use was a server-wide configuration that could not be changed per web application. The default value is
standard-session-cache. See Section 17.3, “Configure the JBoss Cache instance used for session state replication” for more details on JBoss Cache configuration for web-tier clustering.
- Specifies whether all replication messages associated with a request will be batched into one message. This is applicable only if
replication-field-batch-modeis set to
true, fine-grained changes made to objects stored in the session attribute map will replicate only when the HTTP request is finished; otherwise they replicate as they occur. Setting this to
falseis not advised because it increases the number of replication requests and the chance of session state being out of sync. Default is
FIELDgranularity option is now deprecated as JBoss Cache, which provides this feature, is to be subsituted by Infinispan (Infinispan does not support this granularity).
- Specifies whether the container should assume that a JK-based software load balancer (for example,. mod_jk, mod_proxy, mod_cluster) is being used for load balancing for this web application. If set to
true, the container will examine the session ID associated with every request and replace the
jvmRouteportion of the session ID if it detects a failover.You need only set this to
falsefor web applications whose URL cannot be handled by the JK load balancer.
- Specifies the maximum interval between requests, in seconds, after which a request will trigger replication of the session's timestamp regardless of whether the request has otherwise made the session dirty. Such replication ensures that other nodes in the cluster are aware of the most recent value for the session's timestamp and will not incorrectly expire an unreplicated session upon failover. It also results in correct values for
HttpSession.getLastAccessedTime()calls following failover.The default value is
null(in effect, unspecified). In this case the session manager will use the presence or absence of a
jvmRouteconfiguration on its enclosing JBoss Web
Engine(see Section 3.2, “Configuring JBoss to work with mod_jk”) to determine whether JK is used.A value of
0means the timestamp will be replicated whenever the session is accessed. A value of
-1means the timestamp will be replicated only if some other activity during the request (for example,. modifying an attribute) has resulted in other replication work involving the session. A positive value greater than the
HttpSession.getMaxInactiveInterval()value will be treated as probable misconfiguration and converted to
0; (in effect, replicate the metadata on every request). Default value is
- Specifies when sessions are replicated to the other nodes. Possible values are
INSTANT(the default) and
INTERVAL.The typical value,
INSTANT, replicates changes to the other nodes at the end of requests, using the request processing thread to perform the replication. In this case, the
snapshot-intervalproperty is ignored.With
INTERVALmode, a background task is created that runs every
snapshot-intervalmilliseconds, checking for modified sessions and replicating them.Note that this property has no effect if
replication-granularityis set to
FIELD. If it is
INSTANTmode will be used.
- Specifies how often (in milliseconds) the background task that replicates modified sessions should be started for this web application. Only meaningful if
snapshot-modeis set to
- Specifies the fully qualified class name of the implementation of the
ClusteredSessionNotificationPolicyinterface that should be used to govern whether servlet specification notifications should be emitted to any registered
ImportantEvent notifications that may be appropriate in non-clustered environment may not necessarily be appropriate in a clustered environment; see https://jira.jboss.org/jira/browse/JBAS-5778 for an example of why a notification may not be desired. Configuring an appropriate
ClusteredSessionNotificationPolicygives the application author fine-grained control over what notifications are issued.