hi, we have a problem with our website for a while.
I tracked it down to a memory-ressource-issue due to memory-requirements for compiling. We can throw memory at the problem to circumvent it, but it looks weird to me. Regardless we have set "development" to true or false in conf/web.xml, , whenever i recursively crawl our website with wget (cleaning work dir before to make sure each page is being compiled again), i can easily trigger an out-of-memory condition in the JVM. When development=false, then i cannot trigger it when i did re-compile every jsp in several steps (with restarting tomcat). With VisualVM (part of jdk) i found that after wget -r crawl, there are 13 million instances of the following classes: org.apache.jasper.compiler.Mark org.apache.jasper.compiler.Node$TemplateText My understanding from a compile run is, that it`s something which is done once and then it`s ready and done and nothing is left in memory. We have some ten-thousands JSPs, i`m not sure how many being crawled with wget, but i don`t get the point why i see ressources being allocated from org.apache.jasper.compiler and not being freed after compile run. Does anybody have a clue ? Is this to be expected, and if yes - why ? Maybe the following bugreport is interesting in this context: https://bz.apache.org/bugzilla/show_bug.cgi?id=44383 regards Roland ps: Tomcat 7.0.42 and 8.0.32 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
