2012-05-15 33 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