Memcache problems

26 views
Skip to first unread message

James Broberg

unread,
Feb 11, 2011, 3:33:03 AM2/11/11
to google-a...@googlegroups.com
Hi folks,

Just set up a new dev environment on Linux with an existing codebase
of mine and came across an odd error I hadn't encountered before.

Has anyone seen the below error? I'm fairly certain memcache is the
problem, not appstats, as I get a similar "java.lang.NoSuchFieldError:
alwaysUseFieldBuilders" error any time I do anything memcache related.

HTTP ERROR 500

Problem accessing /stats. Reason:

alwaysUseFieldBuilders
Caused by:

java.lang.NoSuchFieldError: alwaysUseFieldBuilders
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto.access$5600(StatsProtos.java:3026)
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.maybeForceBuilderInitialization(StatsProtos.java:3590)
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.<init>(StatsProtos.java:3582)
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.create(StatsProtos.java:3597)
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto$Builder.access$5400(StatsProtos.java:3567)
at com.google.appengine.tools.appstats.StatsProtos$RequestStatProto.newBuilder(StatsProtos.java:3554)
at com.google.appengine.tools.appstats.MemcacheWriter.begin(MemcacheWriter.java:94)
at com.google.appengine.tools.appstats.AppstatsFilter.doFilter(AppstatsFilter.java:117)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:58)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:122)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:70)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:349)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

cheers

James

James Broberg

unread,
Feb 13, 2011, 6:10:55 PM2/13/11
to google-a...@googlegroups.com
It was a dumb missing jar error, nothing to see here.

Ashley Schroder

unread,
Feb 24, 2011, 5:14:39 PM2/24/11
to Google App Engine
Just to add some extra info here in case it helps someone.

I got this error while running my tests. It started when I updated
from an older version of the App Engine SDK to 1.4.2. The jar files I
had on my integration test classpath were from the old version and I
needed to update them by overwritin them from the new distribution.

The files in question were:
appengine-api-labs.jar
appengine-api-stubs.jar
appengine-api.jar
appengine-testing.jar

And appengine-testing.jar is actually on the classpath for compiling
the tests, the others are just required as runtime dependencies.

Cheers,
Ashley

On Feb 14, 12:10 pm, James Broberg <jbrob...@gmail.com> wrote:
> It was a dumb missing jar error, nothing to see here.
>
Reply all
Reply to author
Forward
0 new messages