How big is the data?  I believe if its larger than the cache server is 
configured to support it simply isn't stored.

----- Original Message ----
From: André Cruz <[EMAIL PROTECTED]>
To: memcached <[email protected]>
Sent: Friday, December 21, 2007 3:35:03 AM
Subject: java memcached client


Hello all.

I've been using the java memcached API (v1.6[.1])
 (http://www.whalin.com/memcached/ 
) for some months now. Lately I've been seeing a strange problem.

Some adds fail (return false) but when I try to get the key I was  
trying to add, the key is there and with the correct value. And no,  
the key was not there before the add.
Here are some logs:

2007-12-19 23:47:22,623 [TP-Processor45] DEBUG  
pt.sapo.storage.MemcacheStorer - Preparing to store session email =
 [EMAIL PROTECTED] 
  date = Wed Dec 19 23:47:22 WET 2007
2007-12-19 23:47:22,623 [TP-Processor45] INFO   
com.danga.MemCached.MemCachedClient - ++++ serializing for key:  
sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b for class:  
pt.sapo.model.SSOSession
2007-12-19 23:47:22,623 [TP-Processor45] INFO   
com.danga.MemCached.MemCachedClient - ++++ memcache cmd (result code):
  
add sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b 8  
1198111642 165
(NOT_FOUND)
2007-12-19 23:47:22,623 [TP-Processor45] ERROR  
com.danga.MemCached.MemCachedClient - ++++ error storing data in cache
  
for key: sapo_sso_session%3A1ca2fabf-dd55-4a2d-93d3-90bc7f44368b --  
length: 165
2007-12-19 23:47:22,623 [TP-Processor45] ERROR  
com.danga.MemCached.MemCachedClient - NOT_FOUND
2007-12-19 23:47:22,624 [TP-Processor45] ERROR  
pt.sapo.storage.MemcacheStorer - Add returned false for key  
sapo_sso_session:1ca2fabf-dd55-4a2d-93d3-90bc7f44368b

It seems the add is returning NOT_FOUND?! This return value is not in  
the memcached API documentation so it seems strange. I have 8 memcache
  
servers configured, maybe some concurrency problems between the  
threads and this is the result to another command?

I've tried to contact Greg Whalin but got no answer. Has anyone seen  
this problem before?

The memcache server version is 1.1.12, a bit old, but I checked the  
changelog and didn't find anything related to a bug of this kind so it
  
seems it's in the java API I'm using.

Best regards,
André Cruz





      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

Reply via email to