Azure中的Memcached会话pipe理器：连接被强制closures

我正在使用Memcached会话pipe理器以非粘滞模式处理Tomcat会话。 我在Azure中的部署由一个工作者angular色组成，两个实例连接到运行我的Memcached服务器的Azure虚拟机。

一切工作都很好，我的会话被持久化，并透明地检索两个实例中的任何一个。 当会话闲置约4分钟时出现问题; 所有的事情都指出Azure负载平衡器在一段时间不活动之后closures到虚拟机的间谍caching连接。

我的MSMconfiguration是这样的：

<Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager" memcachedNodes="n1:my-azure-vm.cloudapp.net:11211" sticky="false" sessionBackupAsync="false" sessionBackupTimeout="10000" lockingMode="uriPattern:/path1|/path2" requestUriIgnorePattern=".*\.(ico|png|gif|jpg|css|js|ttf|eot|svg|woff)$" transcoderFactoryClass="de.javakaffee.web.msm.serializer.kryo.KryoTranscoderFactory" customConverter="de.javakaffee.web.msm.serializer.kryo.HibernateCollectionsSerializerFactory"/> 

由spymemcached客户端打印的stacktrace是这样的：

• 如何将新的Ubuntu Server与Windows Azure上的虚拟networking相关联？
• 如何保护Azure内的通信？
• 将数据从SQLEXPRESS本地数据库迁移到SQL Azure
• 在非高峰时段，Azure Web和Workerangular色的工作是否已经存在？
• 将SQL数据库连接到网站

 INFO net.spy.memcached.MemcachedConnection: Reconnecting due to exception on {QA sa=/10.194.132.206:13000, #Rops=1, #Wops=0, #iq=0, topRop=net.spy.memcached.protocol.binary.StoreOperationImpl@1d95da8, topWop=null, toWrite=0, interested=1} java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at net.spy.memcached.MemcachedConnection.handleReads (MemcachedConnection.java:303) at net.spy.memcached.MemcachedConnection.handleIO (MemcachedConnection.java:264) at net.spy.memcached.MemcachedConnection.handleIO (MemcachedConnection.java:184) at net.spy.memcached.MemcachedClient.run(MemcachedClient.java:1298) 

鉴于Azure中的空闲时间限制，是否有其他方法可以使MSM在azure色的云中工作？

 package de.javakaffee.web.msm; public class MyMsm extends MemcachedBackupSessionManager { @Override public void backgroundProcess() { super.backgroundProcess(); final MemcachedNodesManager nodesManager = _msm.getMemcachedNodesManager(); // got through all configured node ids and ping each memcached // with a dummy key. // _msm.newSessionId("ping") generates eg ping-n1 for a nodeId n1 // so this will be routed the related memcached node for (String nodeId : nodesManager.getPrimaryNodeIds()) { // use async here so that no error handling is needed _msm.getMemcached().asyncGet(_msm.newSessionId("ping")); } } }