tomcat-cluster-redis-session-manager-2.0.3

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

Downloads:

• tomcat-cluster-redis-session-manager.zip - complete package

Changes Log:

* Bug fixes.
* Fix :: Redis TTL and MaxInactiveInterval issue
* Enhancement :: Redis clustering password supportability

tomcat-cluster-redis-session-manager-2.0.2

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

Downloads:

• tomcat-cluster-redis-session-manager.zip - complete package

Changes Log:

* Bug fixes.
* Fix :: The method "setMaxInactiveInterval" of session is not effective.

tomcat-cluster-redis-session-manager-2.0.1

Tomcat clustering with Redis data-cache implementation.

Redis session manager is plug-gable 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 (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.

It supports, both redis stand-alone and multiple node cluster based on the redis-data-cache.properties configuration.

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

Supports:

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

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

Downloads:

• tomcat-cluster-redis-session-manager.zip - complete package

Changes Log:

• Bug fixes.
• Tomcat 7.x, 8.x & 9.x version supportability changes.

tomcat-cluster-redis-session-manager-2.0

Tomcat clustering with Redis data-cache implementation.

Redis session manager is plug-gable 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 (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.

It supports, both redis stand-alone and multiple node cluster based on the redis-data-cache.properties configuration.

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

Supports:
* Apache Tomcat 7
* Apache Tomcat 8

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

Downloads:
* tomcat-cluster-redis-session-manager.zip - complete package

Changes Log:

 * Bug fixes.
 * Removed redundant and unused codes.
 * Introduced new context for maintaining current session data.
 * Tomcat 7.x & 8.x version supportability changes.

Migration Procedure:

 * Replace redis data-cache properties in tomcat/conf directory.
 * Update the below lines in tomcat/conf/context.xml file.
        <Valve className="tomcat.request.session.redis.SessionHandlerValve" />
        <Manager className="tomcat.request.session.redis.SessionManager" />

tomcat-cluster-redis-session-manager-1.1.1

Welcome to Tomcat 8 Redis session manager

Redis session manager is plug-gable 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 (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.

It supports, both single redis master and redis cluster based on the RedisDataCache.properties configuration.

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

Supports:

• Apache Tomcat 8

Tomcat Redis Cluster Enabled Session Manager is available in below location

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

---

Changes log:

Code modified for Redis database selection and connection timeout from default value to configurable value.

For this, I've added the below mentioned properties in "RedisDataCache.properties" configuration file,

 # Redis database (default 0)
      redis.database=0

 # Redis connection timeout (default 2000)
      redis.timeout=2000

 Note: Both the properties are not mandatory.

tomcat-cluster-redis-session-manager-1.1

Welcome to Tomcat 8 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 (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.

It supports, both single redis master and redis cluster based on the RedisDataCache.properties configuration.

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

Supports:

• Apache Tomcat 8

Tomcat Redis Cluster Enabled Session Manager is available in below location

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

tomcat-cluster-redis-session-manager-1.0

Welcome to Tomcat 7 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 (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.

It supports, both single redis master and redis cluster based on the RedisDataCache.properties configuration.

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

Supports:

• Apache Tomcat 7

Tomcat Redis Cluster Enabled Session Manager is available in below location

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