This topic provides information about sticky load balancers, session expiration, additional VMware Tanzu GemFire property changes, and serialization in Tanzu GemFire.
Sticky Load Balancers
Typically, session replication is 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 Tanzu 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 Tanzu GemFire servers when running in client-server mode.
Making Additional Tanzu GemFire Property Changes
To change additional Tanzu GemFire property values, refer to one of the following sets of instructions to manually change property values:
- Tomcat: Changing the Default GemFire Configuration in the Session Management Extension
- AppServers: Changing the Default GemFire in Session Management for AppServers
Extension Version Information
To acquire Tanzu GemFire extension version information, examine the web server’s log file for a message similar to:
INFO: Initializing Tanzu GemFire Modules
Java version: 1.0.0 user1 041216 2016-11-12 11:18:37 -0700
javac 1.8.0_361
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 HTTP Session Management extensions must be serializable because the session’s objects are serialized before being stored in the region.
