4459da5696 | 5 years ago | |
---|---|---|
.. | ||
redisson-tomcat-7 | 5 years ago | |
redisson-tomcat-8 | 5 years ago | |
redisson-tomcat-9 | 5 years ago | |
README.md | 5 years ago | |
pom.xml | 5 years ago |
README.md
Redis based Tomcat Session Manager
Stores session of Apache Tomcat in Redis and allows to distribute requests across a cluster of Tomcat servers. Implements non-sticky session management backed by Redis.
Supports Apache Tomcat 7.x, 8.x, 9.x
Consider Redisson PRO version for advanced features and support by SLA.
Advantages
Current implementation differs from any other Redis based Tomcat Session Manager in terms of efficient storage and optimized writes. Each session attribute is written into Redis during each HttpSession.setAttribute
invocation. While other solutions serialize whole session each time.
Usage
1. Add RedissonSessionManager
Add RedissonSessionManager
into tomcat/conf/context.xml
<Manager className="org.redisson.tomcat.RedissonSessionManager"
configPath="${catalina.base}/redisson.conf"
readMode="REDIS" updateMode="DEFAULT" broadcastSessionEvents="false"/>
readMode
- read Session attributes mode. Two modes are available:
MEMORY
- stores attributes into local Tomcat Session and Redis. Further Session updates propagated to local Tomcat Session using Redis-based events.REDIS
- stores attributes into Redis only. Default mode.
broadcastSessionEvents
- if true
then sessionCreated
and sessionDestroyed
events are broadcasted across all Tomcat instances and cause all registered HttpSessionListeners to be triggered. Default is false
.
updateMode
- Session attributes update mode. Two modes are available:
DEFAULT
- session attributes are stored into Redis only through setAttribute method. Default mode.AFTER_REQUEST
- all session attributes are stored into Redis after each request.
configPath
- path to Redisson JSON or YAML config. See configuration wiki page for more details.
Shared Redisson instance
RedissonSessionManager
is created per Web Application and thus creates own Redisson instance. For multiple applications, which use the same Redis setup, amount of Redisson instances could be reduced using JNDI registry:
- Add shared redisson instance produced by
JndiRedissonFactory
intotomcat/conf/server.xml
inGlobalNamingResources
tag area:
<GlobalNamingResources>
<Resource name="bean/redisson"
auth="Container"
factory="org.redisson.JndiRedissonFactory"
configPath="${catalina.base}/conf/redisson.yaml"
closeMethod="shutdown"/>
</GlobalNamingResources>
- Add
JndiRedissonSessionManager
with resource link to redisson instance intotomcat/conf/context.xml
<ResourceLink name="bean/redisson"
global="bean/redisson"
type="org.redisson.api.RedissonClient" />
<Manager className="org.redisson.tomcat.JndiRedissonSessionManager"
readMode="REDIS"
jndiName="bean/redisson" />
2. Copy two jars into TOMCAT_BASE/lib
directory:
for Tomcat 7.x
redisson-tomcat-7-3.11.6.jar
for Tomcat 8.x
redisson-tomcat-8-3.11.6.jar
for Tomcat 9.x
redisson-tomcat-9-3.11.6.jar