Closed GoogleCodeExporter closed 9 years ago
Having been in a similar situation recently (although not with Groovy), I can
say this is a class loading problem and not a spymemcached issue.
The thing to check is that the serialized class and the spy memcached library
are part of the same class loader. In my case, just to illustrate an example, I
was seeing the CNFE because my memcached jar was in tomcat/common/lib, while my
serialized class was part of my webapp (app/WEB-INF/classes). This causes the
CNFE because the memcached library doesn't "see" the webapp's class that was
cached. Moving the library from common/lib to app/WEB-INF/lib takes care of
this.
Original comment by morales....@gmail.com
on 4 Apr 2011 at 1:23
Thanks It worked for me.
Original comment by pankajav...@gmail.com
on 28 Apr 2011 at 2:12
This appears to be an issue on the user side. Closing the issue for now. If
this is still an issue please reopen the bug.
Original comment by mikewie...@gmail.com
on 17 Aug 2012 at 5:51
If you're in the cloud with a service provider like Heroku where you can't
simply change the jar placement in app server directories ... the tip given
here is more effective as a workaround:
http://code.google.com/p/spymemcached/issues/detail?id=155#c2
Original comment by pulkitsi...@gmail.com
on 5 Feb 2013 at 10:01
Original issue reported on code.google.com by
Alexande...@gmail.com
on 4 Jul 2010 at 12:04