I've posted a reply to the issue, which I'm copying below: Unlike production, the dev_appserver's memcache implementation has a 100M limit which it will happily attempt to fill, regardless of how much heap space you actually have free in your JVM. You can either increase your heap size to accomodate the limit, or change the limit to accomodate your heap size. You can change the limit by setting the system property, memcache.maxsize. For example,
$SDK_HOME/bin/dev_appserver.sh --jvm_flag=-Dmemcache.maxsize=50M On Tue, Nov 24, 2009 at 12:59 PM, Vince Bonfanti <vbonfa...@gmail.com>wrote: > There appears to be a memory leak with the memcache implementation on the > dev server; I've opened a new issue for this: > > http://code.google.com/p/googleappengine/issues/detail?id=2428 > > I have some testcases that make heavy use of memcache that are failing due > to this issue. > > Vince > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
