This section provides information on sticky load balancers, session expiration, additional VMware GemFire property changes, serialization and more.
Sticky Load Balancers
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).
Session Expiration
To set the session expiration value, you must change the session-timeout value specified in your application server’s WEB-INF/web.xml file. This value will override the VMware GemFire inactive interval, which is specified in Tomcat, for example, by maxInactiveInterval within context.xml.
When a session expires, it gets removed from the application server and from all VMware GemFire servers when running in client-server mode.
Making Additional VMware GemFire Property Changes
If you want to change additional VMware GemFire property values, refer to instructions on manually changing property values as specified in the VMware GemFire module documentation for Tomcat (Changing the Default VMware GemFire Configuration in the Tomcat Module) and Application Servers (Changing the Default VMware GemFire Configuration in the AppServers Module).
Module Version Information
To acquire VMware GemFire module version information, look in the web server’s log file for a message similar to:
INFO: Initializing VMware GemFire Modules
Java version: 1.0.0 user1 041216 2016-11-12 11:18:37 -0700
javac 1..0_272
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
Object Serialization
Objects managed by the HTTP Session Management Module must be serializable since the session’s objects are serialized before being stored in the region.
