负载均衡下的多台tomcat服务器，通过memcache实现session共享

session共享的应用场景

大型分布式网站，通常使用的架构是，硬件均衡设备(cisco以太网通道、windows nlb技术、linux lvs技术、f5等负载均衡器)——>多台Squid、nginx服务器（反向代理、负载均衡）——>weserver（tomcat，jboss，jetty，nginx等）——>cache集群（redis、memcache、一些企业自己实现的分布式缓存框架）——>关系和非关系型数据库

在以上架构中，需要保持aap1中多台服务器和app2中多台服务器的session同步，并且当一台webserver宕机后，会话不丢失。

决绝方案有

1、session持久化到db。

2、存储在缓存集群上。这种方式的缺点，一旦缓存重启，session丢失。

采用以上方案后，也同时达到了一台webserver宕机后，会话不丢失的目的。

memcached-session-manager

1、memcached-session-manager是一个开源的tomcat session 共享解决方案。

2、他支持sticky、non-sticky模式

3、sticky模式

使请求被映射到同一个webserver，

webserver正常服务：session保持在本地，请求处理完成，同步到后台memcache。

webserver宕机，请求被转发到其他webserver：其他webserver从memcache取得session，恢复会话。

4、non-sticky模式

为请求提供服务的webserver是不确定的。当请求到来时，从memcache中加载session，处理完成，将session写回。

基于memcache，通过memcached-session-manager实现session共享

环境

redhat6.4

tomcat7

nginx1.6.3

memcache 1.4.25

1、tomcat安装

2、nginx安装

http://blog.csdn.net/iktz_cn/article/details/50075183，基本是命令，直接敲下来就ok了。

3、memcache安装

wget http://memcached.org/files/memcached-1.4.25.tar.gz

tar -zxvf memcached-1.4.25.tar.gz

cd memcached-1.4.25

./configure 

error-01
checking for libevent directory... configure: error: libevent is required.  You can get it from http://www.monkey.org/~provos/libevent/


      If it's already installed, specify its path using --with-libevent=/dir/

wget http://124.205.69.135/files/3244000000F59930/downloads.sourceforge.net/project/levent/libevent/libevent-2.0/libevent-2.0.22-stable.tar.gz
tar -zxvf libevent-2.0.22-stable.tar.gz
cd libevent-2.0.22-stable
./configure && make && make install

find / -name "libevent*" 可知道 livevent 安装在/usr/local/lib/下

找到 libevent is required

在 if test $le_found = no ; then 上边加上一行  le_found="/usr/local/lib/" ，保存退出

cd memcached-1.4.25

./configure && make && make install

以下信息说明了memcache命令被安装到了/usr/local/bin 下

make[3]: Entering directory `/root/memcached-1.4.25'
 /bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c memcached '/usr/local/bin'
 /bin/mkdir -p '/usr/local/include/memcached'
 /usr/bin/install -c -m 644 protocol_binary.h '/usr/local/include/memcached'

error_02
[root@web01 lib64]# memcached 
memcached: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory

ldd /usr/local/bin/memcached

[root@web01 lib64]# ldd /usr/local/bin/memcached
linux-vdso.so.1 =>  (0x00007fff8fcdb000)
<span style="color:#cc0000;">libevent-2.0.so.5 => not found</span>
librt.so.1 => /lib64/librt.so.1 (0x00007fe348e0d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe348bf0000)
libc.so.6 => /lib64/libc.so.6 (0x00007fe34885d000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe34901c000)

find / -name "libevent-2.0.so.5"
[root@web01 lib64]# find / -name "libevent-2.0.so.5"
/usr/local/lib/libevent-2.0.so.5

ln -s /usr/local/lib/libevent-2.0.so.5  /lib64/libevent-2.0.so.5

[root@web01 lib64]# ldd /usr/local/bin/memcached
linux-vdso.so.1 =>  (0x00007fffa5de8000)
<span style="color:#cc0000;">libevent-2.0.so.5 => /lib64/libevent-2.0.so.5 (0x00007fb2c2f8e000)</span>
librt.so.1 => /lib64/librt.so.1 (0x00007fb2c2d86000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb2c2b68000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb2c27d5000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb2c31d9000)

启动

memcached -uroot -d -m 1024  -p 11211

[root@web01 lib64]# ps -ef |grep memcached
root     16875     1  0 23:37 ?        00:00:00 memcached -uroot -d -m 1024 -p 11211
root     16882  3667  0 23:37 pts/0    00:00:00 grep memcached

加上 -vv 参数可以打印状态到控制台

4、项目部署

5、整合

a、拷贝jar包到tomcat的lib目录

memcached-session-manager-1.9.0-RC1.jar

memcached-session-manager-tc7-1.9.0-RC1.jar

spymemcached-2.8.4.jar

b、在${tomcat_home}/conf/context.xml下，加入以下内容

<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
        memcachedNodes="n1:192.168.1.108:11211"
        sticky="false"
        sessionBackupAsync="false"
        requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js)$"
        transcoderFactoryClass="de.javakaffee.web.msm.serializer.kryo.KryoTranscoderFactory"
/>

b、web应用中加入依赖

<dependency>
    <groupId>de.javakaffee.msm</groupId>
    <artifactId>msm-kryo-serializer</artifactId>
    <version>1.6.2</version>
</dependency>

c、启动tomcat

error_02

原因：memcached-session-manager-tc7 这个包最后的tc7指的是tomcat的版本，在tc8中，是没有getContext()方法的。若用的是tomcatX，下载tcX的包.对应即可。

org.apache.catalina.LifecycleException: Failed to start component [de.javakaffee.web.msm.MemcachedBackupSessionManager[/ms]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5476)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1247)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1898)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: de.javakaffee.web.msm.MemcachedBackupSessionManager.getContext()Lorg/apache/catalina/Context;
at de.javakaffee.web.msm.MemcachedBackupSessionManager.getSessionCookieName(MemcachedBackupSessionManager.java:823)
at de.javakaffee.web.msm.MemcachedSessionService.startInternal(MemcachedSessionService.java:429)
at de.javakaffee.web.msm.MemcachedBackupSessionManager.startInternal(MemcachedBackupSessionManager.java:518)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 12 more

d、对memcache状态进行监控

系统部署好后，进行登录、退出等操作。可以看到memcache的状态变化。

telnet 192.168.1.108 11211

status

<36 new auto-negotiating client connection
36: Client using the ascii protocol
<36 get ping-n1
>36 END
<36 set 019C1D13721091633AEEA7FEA666A3F6-n1 2048 3600 89
>36 STORED
<36 set validity:019C1D13721091633AEEA7FEA666A3F6-n1 2048 1800 20
>36 STORED
<36 get ping-n1
>36 END
<36 get 019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key 019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 get validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 set 019C1D13721091633AEEA7FEA666A3F6-n1 2048 3600 139
>36 STORED
<36 set validity:019C1D13721091633AEEA7FEA666A3F6-n1 2048 1800 20
>36 STORED
<36 get ping-n1
>36 END
<36 get 019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key 019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 get validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 set validity:019C1D13721091633AEEA7FEA666A3F6-n1 2048 1800 20
>36 STORED
<36 add 019C1D13721091633AEEA7FEA666A3F6-n1 512 5 1
>36 NOT_STORED
<36 get ping-n1
>36 END
<36 get 019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key 019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 get validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 sending key validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 END
<36 delete 019C1D13721091633AEEA7FEA666A3F6-n1
>36 DELETED
<36 delete validity:019C1D13721091633AEEA7FEA666A3F6-n1
>36 DELETED
<36 set 521F60ECF60614F70E8A3ED51F92816C-n1 2048 3600 89
>36 STORED
<36 set validity:521F60ECF60614F70E8A3ED51F92816C-n1 2048 1800 20
>36 STORED