设为首页 收藏本站
查看: 2062|回复: 0

[经验分享] jetty-redis共享session

[复制链接]

尚未签到

发表于 2016-12-18 11:32:09 | 显示全部楼层 |阅读模式
jetty-session-redis  

Jetty session clustering with REDIS

    REDIS website (tested on version 2.2.1)
    JEDIS website (tested on version 1.5.2)
    Jetty website (tested on version 8.0.0.M2)

Build instruction:

git clone git://github.com/Ovea/jetty-session-redis.git
cd jetty-session-redis
mvn package

Download

All downloads are here. They will also be available in Maven central repository and also in Sonatype OSS repositories soon:

    Snapshots - in Sonatype OSS Repository
    Releases - in Sonatype OSS Repository
    Releases - in Maven Central Repository

See the section below to know which package you need (the jar file or the -all bundle).
Installation

You need to put in Jetty's lib/ext folder:

    jedis                     // https://github.com/downloads/xetorthio/jedis/jedis-2.1.0.jar
    commons-pool   // http://mirrors.cnnic.cn/apache//commons/pool/binaries/commons-pool-1.6-bin.tar.gz

and one of the following JAR:

    jetty-session-redis-X.Y.jar (if you are going to put all serializer dependencies also as independant jar files)
    jetty-session-redis-X.Y-all.jar (contains already packaged-relocated serializers)

I strongly recommand you use the jetty-session-redis-X.Y-all.jar because some serializers (like JBoss Serializer) have been improved for performance.
Configuration

In Jetty server configuration file (i.e. jetty.xml):

<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
<Configure id="Server" class="org.eclipse.jetty.server.Server">

    <!--
        Configure session id management
    -->
    <Set name="sessionIdManager">
        <New class="com.ovea.jetty.session.redis.RedisSessionIdManager">
            <Arg>
                <Ref id="Server"/>
            </Arg>
            <Arg>session/redis</Arg>
            <!-- time interval to check for expired sessions in redis cache, in milliseconds. Defaults to 1 min -->
            <Set name="scavengerInterval">30000</Set>
            <!-- cluster node name -->
            <Set name="workerName">
                <SystemProperty name="jetty.node" default="node1"/>
            </Set>
        </New>
    </Set>

    <!--
        Provides a Redis Pool for session management on server and each webapp
    -->
    <New class="org.eclipse.jetty.plus.jndi.Resource">
        <Arg>session/redis</Arg>
        <Arg>
            <New class="redis.clients.jedis.JedisPool">
                <Arg>
                    <New class="org.apache.commons.pool.impl.GenericObjectPool$Config">
                        <Set type="int" name="minIdle">5</Set>
                        <Set type="int" name="maxActive">15</Set>
                        <Set type="boolean" name="testOnBorrow">true</Set>
                    </New>
                </Arg>
                <Arg>127.0.0.1</Arg>
                <Arg type="int">6379</Arg>
            </New>
        </Arg>
    </New>

</Configure>

In each web application context file using session clustering (i.e. in WEB-INF/jetty-env.xml):

<Configure id="webappContext" class="org.eclipse.jetty.webapp.WebAppContext">

    <Set name="contextPath">/webapp1</Set>

    <Set name="sessionHandler">
        <New class="org.eclipse.jetty.server.session.SessionHandler">
            <Arg>
                <New class="com.ovea.jetty.session.redis.RedisSessionManager">
                    <Arg>session/redis</Arg>
                    <Arg>
                        <New class="com.ovea.jetty.session.serializer.JsonSerializer"/>
                    </Arg>
                    <!-- set the interval in seconds to force session persistence event if it didn't changed. Default to 60 seconds -->
                    <Set name="saveInterval">20</Set>
                    <!-- set the cookie domain -->
                    <Set name="sessionDomain">127.0.0.1</Set>
                    <!-- set the cookie path -->
                    <Set name="sessionPath">/</Set>
                    <!-- set the cookie max age in seconds. Default is -1 (no max age). 1 day = 86400 seconds -->
                    <Set name="maxCookieAge">86400</Set>
                    <!-- set the interval in seconds to refresh the cookie max age. Default to 0. This number should be lower than the session expirity time. -->
                    <Set name="refreshCookieAge">300</Set>
                </New>
            </Arg>
        </New>
    </Set>

</Configure>

Note: Jetty's default for maxCookieAge is -1 and as per my tests, setting it to a too short value may cause issues in session retrieval.
Controlling session serialization

By default, session attributes are serialized using XStream, but this is clearly the worst serializer and you must make sure that you configure the serializer according to your needs. If you have small sessions with simple types, consider the JsonSerializer. If you have complexe objects but all serializable, you can consider the JbossSerializer. You can also create your own ones byt implementing the Serializer class of a provided skeleton (see examples here).

Here is the list of provided Serializer:

    com.ovea.jetty.session.serializer.JsonSerializer
    com.ovea.jetty.session.serializer.JdkSerializer
    com.ovea.jetty.session.serializer.XStreamSerializer

    com.ovea.jetty.session.serializer.JBossSerializer

    session/redis

Debugging

If you need to troobleshoot something, you can put Jetty in DEBUG mode and see the traces from RedisSessionManager and RedisSessionIdManager.

Also, with Redis you have the ability to monitor all the calls. Simply issue in a command-line:

redis-cli monitor

To see all Redis requests going to the Redis server. If you are using a String serializer such as XStream of Json, you'll be able to see all your session attributes into.
Versions & Compatibility

The latest release (>= 2.1.ga) must be used with at least these dependencies:

    com.ovea:jetty-session-redis:2.1.ga:serialjson
    org.eclipse.jetty.aggregate:jetty-all:8.0.2.v20111006
    org.mortbay.jetty:servlet-api:3.0.20100224
    redis.clients:jedis:2.0.0
    commons-pool:commons-pool:1.5.6

Authors and help

    Mathieu Carbou mail | blog | website


https://github.com/Ovea/jetty-session-redis

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-315992-1-1.html 上篇帖子: centos6.0 安装redis 下篇帖子: Redis的持久化机制
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表