memcache报错 failed to close SockIO obj from deadPool(已解决)

现象

memcache在频繁的报错

failed to close SockIO obj from deadPool
on Jun 09 11:54:55 CST 2014 - ++++ failed to close SockIO obj from deadPool
com.danga.MemCached.SockIOPool Mon Jun 09 11:54:55 CST 2014 - ++++ socket or its streams already null in trueClose call
java.io.IOException: ++++ socket or its streams already null in trueClose call
        at com.danga.MemCached.SockIOPool$SockIO.trueClose(SockIOPool.java:1704)
        at com.danga.MemCached.SockIOPool.selfMaint(SockIOPool.java:1432)
        at com.danga.MemCached.SockIOPool$MaintThread.run(SockIOPool.java:1497)
com.danga.MemCached.SockIOPool Mon Jun 09 11:54:55 CST 2014 - ++++ failed to close SockIO obj from deadPool
com.danga.MemCached.SockIOPool Mon Jun 09 11:54:55 CST 2014 - ++++ socket or its streams already null in trueClose call

产生原因

网上搜索了下是 memcache 连接数和内存不够

解决方案

将-m和-c调大就ok了
/usr/local/bin/memcached -d -m 1000 -u root -l 127.0.0.1 -p 11211 -c 4560 -P /tmp/memcached.pid

赞(1) 打赏
特别声明:除特殊标注,本站文章均为原创,遵循CC BY-NC 3.0,转载请注明出处。三伏磨 » memcache报错 failed to close SockIO obj from deadPool(已解决)

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏