Sorry for not responding sooner. I have been out of town for the holidays. This does not correspond to any known or reported bug in the Java client I am maintaining and it is in heavy use at quite a few heavy installations. Not saying that it is out of the question, but definitely not something I am aware of. Looking at the debug, the client is simply spitting out the response it received from the server. How have you configured your client install (did you follow the HOWTO document from the site)?
<br><br>gw<br><br><div class="gmail_quote">On Dec 21, 2007 6:35 AM, André Cruz <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all.<br><br>I've been using the java memcached API (v1.6[.1]) (<a href="http://www.whalin.com/memcached/" target="_blank">http://www.whalin.com/memcached/</a><br>) for some months now. Lately I've been seeing a strange problem.
<br><br>Some adds fail (return false) but when I try to get the key I was<br>trying to add, the key is there and with the correct value. And no,<br>the key was not there before the add.<br>Here are some logs:<br><br>2007-12-19 23:47:22,623 [TP-Processor45] DEBUG
<br>pt.sapo.storage.MemcacheStorer - Preparing to store session email = <a href="mailto:XXX@sapo.pt">XXX@sapo.pt</a><br> date = Wed Dec 19 23:47:22 WET 2007<br>2007-12-19 23:47:22,623 [TP-Processor45] INFO<br>com.danga.MemCached.MemCachedClient
- ++++ serializing for key:<br>sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b for class:<br>pt.sapo.model.SSOSession<br>2007-12-19 23:47:22,623 [TP-Processor45] INFO<br>com.danga.MemCached.MemCachedClient - ++++ memcache cmd (result code):
<br>add sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b 8<br>1198111642 165<br>(NOT_FOUND)<br>2007-12-19 23:47:22,623 [TP-Processor45] ERROR<br>com.danga.MemCached.MemCachedClient - ++++ error storing data in cache
<br>for key: sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b --<br>length: 165<br>2007-12-19 23:47:22,623 [TP-Processor45] ERROR<br>com.danga.MemCached.MemCachedClient - NOT_FOUND<br>2007-12-19 23:47:22,624 [TP-Processor45] ERROR
<br>pt.sapo.storage.MemcacheStorer - Add returned false for key<br>sapo_sso_session:1ca2fabf-dd55-4a2d-93d3-90bc7f44368b<br><br>It seems the add is returning NOT_FOUND?! This return value is not in<br>the memcached API documentation so it seems strange. I have 8 memcache
<br>servers configured, maybe some concurrency problems between the<br>threads and this is the result to another command?<br><br>I've tried to contact Greg Whalin but got no answer. Has anyone seen<br>this problem before?
<br><br>The memcache server version is 1.1.12, a bit old, but I checked the<br>changelog and didn't find anything related to a bug of this kind so it<br>seems it's in the java API I'm using.<br><br>Best regards,
<br><font color="#888888">André Cruz</font></blockquote></div><br><br clear="all"><br>-- <br>Greg Whalin