java.lang.OutOfMemoryError
Tomcat ran out of memory; what is causing this?
Submitted by Eelco Visser on 29 May 2010 at 15:08
[root@webdsl:/home/eelcovisser]# tail -f /data/tomcat/logs/catalina.out
at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:342)
… 23 more
Caused by: java.lang.OutOfMemoryError: Java heap space
[Loaded sun.reflect.GeneratedMethodAccessor854 from JVM_DefineClass]
[Loaded sun.reflect.GeneratedMethodAccessor855 from JVM_DefineClass]
[Unloading class sun.reflect.GeneratedMethodAccessor854]
[Unloading class sun.reflect.GeneratedMethodAccessor855]
Issue Log
Isn’t this the same as Issue 24? Or has researchr already been updated?
I have updated researchr since then, and fixed that recursion; or so I believe at least.
Ok, I will run the memory analyzer and try to find out what happened.
At the moment nothing is out of the ordinary on the server. It consumes a normal amount of memory (700M-1700M) and responds well to garbage collection requests. I think the out of memory crashes are caused by shorter events (like the recursion last time). In order to debug this, I need a heap dump just before Tomcat crashes. I will ask Rob to add a switch to Tomcat to make these dumps. Once added, I can debug the problem after the next crash. Let me know if you notice a crash.
Server seems to run smoothly these days. Closing the issue.
Log in to post comments