From c79b5050071120215269ba1614556aa47d93a7cc Mon Sep 17 00:00:00 2001 From: Ranjith Manickam Date: Sun, 2 Dec 2018 23:29:37 +0530 Subject: [PATCH] Updated Home (markdown) --- Home.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Home.md b/Home.md index 4b3c5f8..84cd16d 100644 --- a/Home.md +++ b/Home.md @@ -2,9 +2,9 @@ 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. +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. -It supports, both redis stand-alone and multiple node cluster based on the redis-data-cache.properties 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.