2012-05-15 34 views
0

这与问题Java Appengine APPSTATS causing java out of memory error有关。如何减少Google App Engine上Appstats的内存使用量Java

Appstats似乎在128MB实例上导致java.lang.OutOfMemoryError,我不知道是否有办法减少日志记录的数量。 有没有办法从堆栈跟踪中过滤一些包名?

GAE的API:

@14ms memcache.Get real=7ms api=0ms 
Stack: 
    com.google.appengine.tools.appstats.Recorder:290 makeAsyncCall() 
    com.google.apphosting.api.ApiProxy:184 makeAsyncCall() 
    com.google.apphosting.api.ApiProxy:123 makeAsyncCall() 
    com.google.appengine.api.memcache.MemcacheServiceApiHelper:104 makeAsyncCall() 
    com.google.appengine.api.memcache.AsyncMemcacheServiceImpl:372 doGetAll() 
    com.google.appengine.api.memcache.AsyncMemcacheServiceImpl:333 getIdentifiables() 
    com.google.appengine.api.memcache.MemcacheServiceImpl:61 getIdentifiables() 

我参加办法API:

com.googlecode.objectify.cache.EntityMemcache:215 getAll() 
    com.googlecode.objectify.cache.CachingAsyncDatastoreService:253 get() 
    com.googlecode.objectify.cache.CachingDatastoreService:161 get() 
    com.googlecode.objectify.cache.CachingDatastoreService:147 get() 
    com.googlecode.objectify.cache.CachingDatastoreService:128 get() 
    siena.gae.GaePersistenceManager:231 getByKey() 
    siena.Model:106 getByKey() 
    com.sirtrack.iridium.model.GroupEntity:147 getByKey() 
    com.sirtrack.iridium.task.ProjectUpdateTask:49 doPost() 

无关:

javax.servlet.http.HttpServlet:637 service() 
    javax.servlet.http.HttpServlet:717 service() 
    org.mortbay.jetty.servlet.ServletHolder:511 handle() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1166 doFilter() 
    com.google.appengine.tools.appstats.AppstatsFilter:141 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.SiteFilter:106 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.RewriteFilter:79 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.AuthenticationFilter:83 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.PluginCronFilter:78 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.LanguageFilter:66 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.UpdateFilter:78 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.InitFilter:80 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.vosao.filter.ContextFilter:74 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    com.google.apphosting.utils.servlet.ParseBlobUploadFilter:102 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    com.google.apphosting.runtime.jetty.SaveSessionFilter:35 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    com.google.apphosting.utils.servlet.TransactionCleanupFilter:43 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler$CachedChain:1157 doFilter() 
    org.mortbay.jetty.servlet.ServletHandler:388 handle() 
    org.mortbay.jetty.security.SecurityHandler:216 handle() 
    org.mortbay.jetty.servlet.SessionHandler:182 handle() 
    org.mortbay.jetty.handler.ContextHandler:765 handle() 
    org.mortbay.jetty.webapp.WebAppContext:418 handle() 
    com.google.apphosting.runtime.jetty.AppVersionHandlerMap:249 handle() 
    org.mortbay.jetty.handler.HandlerWrapper:152 handle() 
    org.mortbay.jetty.Server:326 handle() 
    org.mortbay.jetty.HttpConnection:542 handleRequest() 
    org.mortbay.jetty.HttpConnection$RequestHandler:923 headerComplete() 
    com.google.apphosting.runtime.jetty.RpcRequestParser:76 parseAvailable() 
    org.mortbay.jetty.HttpConnection:404 handle() 
    com.google.apphosting.runtime.jetty.JettyServletEngineAdapter:135 serviceRequest() 
    com.google.apphosting.runtime.JavaRuntime$RequestRunnable:446 run() 
    com.google.tracing.TraceContext$TraceContextRunnable:449 runInContext() 
    com.google.tracing.TraceContext$TraceContextRunnable$1:455 run() 
    com.google.tracing.TraceContext:695 runInContext() 
    com.google.tracing.TraceContext$AbstractTraceContextCallback:333 runInInheritedContextNoUnref() 
    com.google.tracing.TraceContext$AbstractTraceContextCallback:325 runInInheritedContext() 
    com.google.tracing.TraceContext$TraceContextRunnable:453 run() 
    com.google.apphosting.runtime.ThreadGroupPool$PoolEntry:251 run() 
    java.lang.Thread:679 run() 

下面是可能造成的逐堆栈跟踪OutOfMemoryError异常的堆栈跟踪:

Error for /_ah/queue/projectupdate 
java.lang.OutOfMemoryError: Java heap space 
    at java.util.Arrays.copyOf(Arrays.java:3057) 
    at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:117) 
    at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:407) 
    at java.lang.StringBuffer.append(StringBuffer.java:241) 
    at java.io.StringWriter.write(StringWriter.java:112) 
    at java.io.PrintWriter.write(PrintWriter.java:429) 
    at java.io.PrintWriter.write(PrintWriter.java:446) 
    at java.io.PrintWriter.print(PrintWriter.java:576) 
    at java.io.PrintWriter.println(PrintWriter.java:712) 
    at java.lang.Throwable.printStackTrace(Throwable.java:529) 
    at com.google.appengine.tools.appstats.Recorder.createStackTrace(Recorder.java:160) 
    at com.google.appengine.tools.appstats.Recorder.initializeIntermediary(Recorder.java:271) 
    at com.google.appengine.tools.appstats.Recorder.makeAsyncCall(Recorder.java:290) 
    at com.googlecode.objectify.cache.TriggerFutureHook.makeAsyncCall(TriggerFutureHook.java:144) 
    at com.google.apphosting.api.ApiProxy.makeAsyncCall(ApiProxy.java:184) 

对于谷歌工程师,这里的a link这些错误

+0

我怀疑这是导致appstats炸弹的堆栈跟踪。 Appstats是一种片状。你绝对可以关闭你不需要它的任何网址,但是你不能截断它的日志输出。 –

+0

@RickMangi我已经更新了我的问题以包含OutOfMemoryError的堆栈跟踪(这是由printStackTrace引起的:D – ZiglioUK

+0

是的,我已经在代码中看到堆栈跟踪,但我认为这是一个症状,而不是根本原因但是我可能是错误的,如果你在记忆体的细冰上滑行,一个大的内存缓存或者一个大的缓冲区写入(像这样)通常会把你推到边缘 –

回答

2

我发现班上com.google.appengine.tools.appstats.Recorder.java称为“maxLinesOfStackTrace”无证(据我所知)参数。

在web.xml:

<filter> 
    <filter-name>appstats</filter-name> 
    <filter-class>com.google.appengine.tools.appstats.AppstatsFilter</filter-class> 
    <init-param> 
     <param-name>maxLinesOfStackTrace</param-name> 
     <param-value>16</param-value> 
    </init-param> 
</filter> 

似乎在本地工作,我会让你知道它是否也有助于避免的OutOfMemoryError。

+0

不错的发现!如果有帮助请更新。 –

+0

预览SDK(1.6.2我认为)他们已经宣布了对Appstats的更改:它们将显示RPC的成本。更多可能出错的东西... – ZiglioUK

+0

我遇到了memcache产生异常的问题,当解决了问题时我会放回Appstats,可能根本没有堆栈跟踪(深度为0或1),应该是足够用于测量RPC。 – ZiglioUK