https://issues.apache.org/bugzilla/show_bug.cgi?id=49249
--- Comment #2 from iJay <mustan...@gmail.com> 2010-05-05 02:16:12 EDT --- (In reply to comment #1) > A quick search gives me this reference: > http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html#par_gc.oom > "The parallel collector will throw an OutOfMemoryError if too much time is > being spent in garbage collection" > > Out of memory errors mean that you must profile your own application to > identify the root cause. See users@ list archives for further pointers. > > http://wiki.apache.org/tomcat/OutOfMemory > http://tomcat.apache.org/bugreport.html#Bugzilla_is_not_a_support_forum > > Closing as INVALID, because there is no Tomcat issue here. I am not a new developer to Java and do know what is a OutOfMemoryError. This application is only a servlet generating dynamic JNLP file and providing JRE download. It ran smoothly during the past one year with load. After we turned "keep alive" on in apache a few days ago, Tomcat crashed this morning. Then we turned it back to off and now it serves with no error. My team supposed that if download a large file from tomcat with keep-alive connection, since all the requests from the same user use the same connection, maybe the stream buffer doesn't close correctly during the download and then cause this ERROR. Pls check in this bug and validate it with patience. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
