Additional Information for HTTP Session Management

Sticky Load Balancers

Typically, session replication will be used in conjunction with a load balancer enabled for sticky sessions. This involves, among other things, establishing a JVM route (JVMRoute=value). Refer to SpringSource ERS as a possible load balancing solution.

Session Expiration

To set the session expiration value, you must change the session-timeout value specified in Tomcat's WEB-INF/web.xml file. This value will override the GemFire inactive interval specified by maxInactiveInterval within context.xml.

Making Additional GemFire Property Changes

If you want to change additional GemFire property values that are not specified in this documentation, refer to instructions on manually changing property values as specified in the GemFire module documentation for Tomcat: HTTP Session Management Module for Tomcat.

Using the gemfire Command-line Tool

GemFire provides the gemfire command-line tool to perform basic administrative tasks. gemfire.sh (for Unix) and gemfire.bat (for Windows) should be located in the /bin subdirectory. Refer to vFabric GemFire Command-Line Utility for more information on this tool.

Module Version Information

To acquire GemFire module version information, look in the web server's log file for the following message:

Nov 8, 2010 12:12:12 PM 
com.gemstone.gemfire.modules.session.catalina.AbstractCacheLifecycleListener 
lifecycleEvent
INFO: Initializing GemFire Modules Version 1.1

Overriding Region Attributes

When using the HTTP Session Management Module, you cannot override region attributes directly on the cache server. You must place all region attribute definitions in the region attributes template that you customize within tc Server. For example, to specify a different name for the region's disk store, you could add the new disk-store-name specification to the region attributes template and then reference the template on the cache server.
<region-attributes id="MY_SESSIONS" refid="PARTITION_REDUNDANT_PERSISTENT_OVERFLOW" 
disk-store-name="mystore">
  ...
</region-attributes>
Then on the cache server side, reference the modified region attributes template to allow the region to use the disk-store-name attribute:
<region name="gemfire_modules_sessions" refid="MY_SESSIONS"/>