Updated Home (markdown)
parent
e8e178a015
commit
f112c2d82f
10
Home.md
10
Home.md
|
@ -1,12 +1,14 @@
|
|||
#### **Welcome to the Tomcat Clustering Redis Session Manager wiki!**
|
||||
|
||||
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 Redis session manager is pluggable one. It stores session into Redis for easy distribution of HTTP Requests across a cluster of Tomcat servers.
|
||||
|
||||
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.
|
||||
Here the Sessions are implemented as non-sticky (means, each request can able to go to any server in the cluster, unlike the Apache provided Tomcat clustering setup.)
|
||||
|
||||
Supports redis default, sentinel and cluster mode, based on the configuration.
|
||||
Request Sessions will be stored into Redis immediately (Session attributes must be Serializable), for the use of other servers. When tomcat receives a request from the client, Sessions are loaded directly from Redis.
|
||||
|
||||
Going forward, we no need to enable sticky session (JSESSIONID) in Load balancer.
|
||||
Supports Redis default, sentinel and cluster mode, based on the configuration.
|
||||
|
||||
Going forward, we no need to enable sticky session (JSESSIONID) in Load Balancer.
|
||||
|
||||

|
||||
|
||||
|
|
Loading…
Reference in New Issue