Hi, Have you checked the return code of the memcache call? Unlike most of the APIs, memcache indicates errors in its return code, rather than throwing an exception.
-Nick Johnson On Tue, Mar 9, 2010 at 6:43 AM, Adhi <adhi.ramanat...@orangescape.com>wrote: > Hi, > Is there any chance that updating memcache fails? In a same > transaction I'm updating a particular record both in memcache and db, > but still the memcache having old data where as db has updated record. > And I have checked the url in stats, the memcache.set is getting > called followed by the db.put(). > > But for the same application it is not happening in different appspot > (staging). Any suggestions or clue? the problem happening in > production. > > Thanks > Adhi > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
