You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Go to file
Ranjith Manickam aa52190ed1
Updated configuration properties.
6 years ago
src Bug fixes and added redis sentinel supportability changes. 6 years ago
.gitignore Updated intellij files. 6 years ago
README.md Updated configuration properties. 6 years ago
pom.xml Bug fixes and added redis sentinel supportability changes. 6 years ago

README.md

Tomcat Clustering Redis Session Manager

Redis session manager is pluggable one. It uses to store sessions into Redis for easy distribution of HTTP Requests across a cluster of Tomcat servers. Sessions are implemented as as non-sticky i.e, each request is forwarded to any server in round-robin manner.

The HTTP Requests session setAttribute(name, value) method stores the session into Redis (session attribute values must be Serializable) immediately and the session getAttribute(name) method request directly from Redis. Also, the inactive sessions has been removed based on the session time-out configuration.

Supports redis default, sentinel and cluster mode, based on the configuration.

Going forward, we no need to enable sticky session (JSESSIONID) in Load balancer.

Supports:

  • Apache Tomcat 7
  • Apache Tomcat 8
  • Apache Tomcat 9

Downloads:

Pre-requisite:

  1. jedis.jar
  2. commons-pool2.jar
  3. commons-logging.jar

more details.. https://github.com/ran-jit/tomcat-cluster-redis-session-manager/wiki

Steps to be done,

  1. Move the downloaded jars to tomcat/lib directory

    • tomcat/lib/
  2. Add tomcat system property "catalina.base"

    • catalina.base="TOMCAT_LOCATION"
      • example: export catalina.base=/opt/tomcat
  3. Extract downloaded package (tomcat-cluster-redis-session-manager.zip) to configure Redis credentials in redis-data-cache.properties file and move the file to tomcat/conf directory

    • tomcat/conf/redis-data-cache.properties
  4. Add the below two lines in tomcat/conf/context.xml

    • <Valve className="tomcat.request.session.redis.SessionHandlerValve" />
    • <Manager className="tomcat.request.session.redis.SessionManager" />
  5. Verify the session expiration time in tomcat/conf/web.xml

    • <session-config>
    •         <session-timeout>60</session-timeout>
    • </session-config>

Note:

  • All your session attribute values must implement java.io.Serializable.
  • Supports redis default, sentinel and cluster mode, based on the redis-data-cache.properties configuration.

Configuration Properties:

<html>
PropertyDescriptionValue
redis.hostsRedis server running instance IP address and port numberdefault: 127.0.0.1:6379
ex: 127.0.0.1:6379, 127.0.0.2:6379, 127.0.0.2:6380, ....
redis.passwordRedis protected password
redis.databaseRedis database selection. (Numeric value)default: 0
redis.timeoutRedis connection timeoutdefault: 2000
redis.cluster.enabledTo enable redis cluster modedefault: false
supported values: true/false
redis.sentinel.enabledTo enable redis sentinel modedefault: false
supported values: true/false
redis.sentinel.masterRedis sentinel master namedefault: mymaster
lb.sticky-session.enabledTo enable redis and standard session mode

If enabled,
  1. Must be enabled sticky session in your load balancer configuration. Else this manager may not return the updated session values
  2. Session values are stored in local jvm and redis
  3. If redis is down/not responding, requests uses jvm stored session values to process user requests. Redis comes back the values will be synced
default: false
</html>