References an existing session management provider Defines a deployment specific Infinispan cache-based session management provider Defines a deployment specific HotRod remote cache-based session management provider References the name of an existing session management provider Defines the granularity of cache entry mapping for the attributes of a session. Indicates the marshalling implementation used for serializing attributes of a session. Web requests will have an affinity for the primary owner of a given session. Behaves the same as local-affinity if the backing cache is not distributed nor replicated. Web requests will have an affinity for the first available node in a list comprised of: primary owner, backup nodes, local node (if not a primary nor backup owner). Behaves the same as local-affinity if the cache is not distributed, nor replicated. Must be explicitly supported by the load balancer. References a cache-container defined by the Infinispan subsystem. References a cache within the associated cache-container. If unspecified, the default cache of the associated cache-container is assumed. Web requests not have an affinity for any particular server. Intended for use cases where web session state is not maintained within the application server. Web requests have an affinity for the member that last handled a given session. This option corresponds to traditional sticky session behavior. References a remote-cache-container defined by the Infinispan subsystem. References a named configuration on the remote server. Configures the number of threads dedicated to processing expiration events from the remote Infinispan cluster. Stores all session attributes within a single cache entry. Generally more expensive than ATTRIBUTE granularity, but preserves any cross-attribute object references. Stores each session attribute within a separate cache entry. Generally more efficient than SESSION granularity, but does not preserve any cross-attribute object references. Session attributes will be marshalled using JBoss Marshalling. Session attributes will be marshalled using ProtoStream. Web requests not have an affinity for any particular server. Intended for use cases where web session state is not maintained within the application server. Web requests have an affinity for the member that last handled a given session. This option corresponds to traditional sticky session behavior. The delimiter used to separate ranked routes within the session ID. The maximum number of routes to append to the session ID. Identifies an immutable session attribute class.