General Information on HTTP Session Management
This section provides information on sticky load balancers, session expiration, additional GemFire property changes, serialization and more.
Typically, session replication will be used in conjunction with a load balancer enabled for sticky sessions.
Sessions should be unique across application servers. With Tomcat, this can be accomplished by setting a JVM route (
JVMRoute=value). Refer to SpringSource ERS
as a possible load balancing solution.
To set the session expiration value, you must change the
session-timeout value specified in your application server’s
This value will override the GemFire inactive interval, which is specified in Tomcat, for example, by
When a session expires, it gets removed from the application server and from all GemFire servers when running in client-server mode.
If you want to change additional GemFire property values, refer to instructions on manually changing property values as specified in the GemFire module documentation for Tomcat (Changing the Default GemFire Configuration in the Tomcat Module) and Application Servers (Changing the Default GemFire Configuration in the AppServers Module).
To acquire GemFire module version information, look in the web server’s log file for a message similar to:
INFO: Initializing GemFire Modules Java version: 1.0.0 user1 041216 2016-11-12 11:18:37 -0700 javac 1.8.0_181 Native version: native code unavailable Source revision: 857bb75916640a066eb832b43b3c805f0dd7ed0b Source repository: develop Running on: /192.0.2.0, 8 cpu(s), x86_64 Mac OS X 10.11.4
Objects managed by the HTTP Session Management Module must be serializable since the session’s objects are serialized before being stored in the region.