基于Java IO 序列化方案的memcached-session-manager多memcached节点配置

 

  在公司项目里想要在前端通过nginx将请求负载均衡，而后台的几组tomcat的session通过memcached(non-sticky模式)进行统一管理，这几组tomcat部署的web app是同一应用，session的变化要统一，项目组最后采用memcached-session-manager来对tomcat的session进行管理。

  session的序列化方案官方推荐的有4种

1. java serialization
2. msm-kryo-serializer
3. msm-javolution-serializer
4. msm-xstream-serializer
   

关于这几种，官方也给出了比较:

 

• Java serialization is very robust and a proven technology. The biggest disadvantage IMHO is that different class versions cannot be handled.
• Kryo is an extremely fast binary serialization library. In the popular thrift-protobuf-compare benchmark it's one of the fastest serialization toolkits - and it differs from the fastest in that it does NOT need a schema definition of serialized data, which is a requirement for serialization arbitrary session data. A disadvantage of using kryo based serialization is that it's binary - you just cannot look how the serialized object graph looks like. This is my favorite serialization strategy, just because of its great performance.
• Javolution is a very good and fast xml binding toolkit. The reflection part is written by me and adds the bits that are actually binding POJOs to xml. It is covered well with unit tests, however I cannot guarantee that there's no issue left to solve (actually this serialization strategy was in use in my own projects, now replaced by kryo based serialization).
• XStream based serialization should be very robust as this is an often used java object binding library. The biggest disadvantage IMHO is the relatively bad performance.

 

要注意的是javolution是唯一支持copyCollectionsForSerialization="true"时对能对线程不安全的collection进行序列化特性的，其他的方案要对序列化线程不安全的collection时特别处理，性能最好的序列化方案是Kryo。

  网上有一些例子都是关于Javolution的，我个人倾向于使用Kryo，至于序列化出现的问题还可以自己解决，不过先使用java IO来配置，先用起来，以后再慢慢优化，换成Kryo。

  直接在$CATALINA_HOME/lib/下添加memcached-2.5.jar和memcached-session-manager-1.4.0.jar，然后对$CATALINA_HOME/conf/server.xml修改相应的配置

 

<Context path="/webapp" docBase="D:\webapp\WebRoot" reloadable="false">
  <Manager
     className= "de.javakaffee.web.msm.MemcachedBackupSessionManager"
     memcachedNodes= "n1:192.168.112.1:11211,n2:192.168.112.2:11211"
     sticky="false"
     lockingMode="auto"
     requestUriIgnorePattern= ".*\.(png|gif|jpg|css|js)$"
     sessionBackupAsync= "false"
     sessionBackupTimeout= "0"
     memcachedProtocol="binary"
     transcoderFactoryClass= "de.javakaffee.web.msm.JavaSerializationTranscoderFactory"
  />
</Context>

<Context path="/webapp" docBase="D:\webapp\WebRoot" reloadable="false">
  <Manager 
     className= "de.javakaffee.web.msm.MemcachedBackupSessionManager"
     memcachedNodes= "n1:192.168.112.1:11211,n2:192.168.112.2:11211" 
     sticky="false" 
     lockingMode="auto" 
     requestUriIgnorePattern= ".*\.(png|gif|jpg|css|js)$"  
     sessionBackupAsync= "false" 
     sessionBackupTimeout= "0" 
     memcachedProtocol="binary"
     transcoderFactoryClass= "de.javakaffee.web.msm.JavaSerializationTranscoderFactory"  
  />
</Context>

 由于项目对session 管理模式是non-sticky的，所以不配置failoverNodes，任何一个web工程对session的修改要及时更新到memcache上，所以sessionBackupTimeout为0(不同的应用有不同的配置，这样配置是符合我现在这个项目要求的)。

评论

3 楼 achenbj 2013-11-28  

我们的问题可能是我们的四个tomcat中的配置不一致造成的，改成一致的之后效果好了点了。

2 楼 achenbj 2013-11-23  

我们这边之前sessionBackupTimeout配置了60，直接报错，最后还是调整到了180000之后才少了些报错。
当时在某些高并发的情况下还是会有上面1楼报的错误，此时登录还是没有什么明显的问题。在注册时会出现较多的问题。
当出现连接不上节点的时候会出现登录注册失败的情况。

还没有找到合适的解决办法。

1 楼 chenjianweicjwjw 2012-04-19  

你这样配置成sessionBackupTimeout="0"不会报错吗？如:2012-4-19 16:28:15 de.javakaffee.web.msm.BackupSessionTask storeSessionInMemcached
信息: Could not store session 22765CC5A113DAB4E64355DAB3131105-n1.jvmtomcat7 in memcached.
2012-4-19 16:28:15 de.javakaffee.web.msm.BackupSessionTask doBackupSession
信息: Could not store session 22765CC5A113DAB4E64355DAB3131105-n1.jvmtomcat7 in memcached due to unavailable node n1.
Note that this session was relocated to this node because the original node was not available.