Open GoogleCodeExporter opened 8 years ago
不是什么假死,是客户端停掉了。
Original comment by killme2...@gmail.com
on 17 Aug 2011 at 3:17
为啥
Original comment by wu.xin...@gmail.com
on 17 Aug 2011 at 3:24
客户端主动停掉了,但是压侧还在继续跑,可能压侧代码写��
�有问题。
Original comment by killme2...@gmail.com
on 17 Aug 2011 at 3:26
我跑的就是你提供的benchmark代码啊
Original comment by wu.xin...@gmail.com
on 17 Aug 2011 at 3:28
我知道,所以我说可能写的有问题,有空我会看下。这个问��
�对你的压测结果没有影响,这个异常也是在这种场景下必须�
��出的。
Original comment by killme2...@gmail.com
on 17 Aug 2011 at 3:36
恩,2个问题:
(1)这个异常也是在这种场景下必须抛出的? 什么场景下
(2)客户端主动停掉了? 为什么会主动停掉?
Original comment by wu.xin...@gmail.com
on 17 Aug 2011 at 3:40
(1)在MemcachedClient被stop之后,继续调用任何操作都应该抛出
MemcachedException,告知用户客户端已停止。
(2)这就是问题所在,benchmark的代码估计有问题,我会看下�
��
Original comment by killme2...@gmail.com
on 17 Aug 2011 at 3:43
net.rubyeye.xmemcached.exception.MemcachedException: Xmemcached is stopped
at net.rubyeye.xmemcached.XMemcachedClient.sendCommand(XMemcachedClient
java:266)
at net.rubyeye.xmemcached.XMemcachedClient.fetch0(XMemcachedClient.java
575)
at net.rubyeye.xmemcached.XMemcachedClient.get0(XMemcachedClient.java:9
7)
at net.rubyeye.xmemcached.XMemcachedClient.get(XMemcachedClient.java:91
)
at net.rubyeye.xmemcached.XMemcachedClient.get(XMemcachedClient.java:92
)
at net.rubyeye.xmemcached.XMemcachedClient.get(XMemcachedClient.java:94
)
at com.snsgame.session.SessionMrg.get(SessionMrg.java:128)
at com.snsgame.session.handler.SessionHandler.sessionLogoff(SessionHand
er.java:51)
at com.server.net.Server.shutdownAll(Server.java:93)
at com.server.net.utils.CloseServer.run(CloseServer.java:18)
问题:客户端在什么情况下会主动停掉??
Original comment by tons...@gmail.com
on 25 Jun 2012 at 7:33
Original issue reported on code.google.com by
wu.xin...@gmail.com
on 17 Aug 2011 at 3:13