Hung server process...

Randy Wigginton krw at
Mon Dec 4 22:59:32 UTC 2006

Hey all,
Been using memcache without any problems... until now.  Running a  
java process under tomcat, it connects to memcache instance with a  
1000 msec connect timeout and a 500 msec read timeout.  Today I found  
a frightening message in my log files:
com.danga.MemCached.SockIOPool Mon Dec 04 17:36:07 EST 2006 - +++  
removing potentially hung connection from busy pool ... socket in  
pool for 3896738ms

Looking in the code, it seems like a hung socket should have been  
detected much sooner.  Another side effect is that tomcat was non- 

Are there any known "hung" conditions for memcache?  This is running  
under java 1.5.0_03

More information about the memcached mailing list