StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I general I would expect the logging code in java to have been well tested. If there is no log output being generated by your logging config it has a low overhead. Your htop results are probably showing some idle thread status in tomcat. </p> <p>It could be logging but you may want to consider <a href="https://stackoverflow.com/questions/6470651/creating-a-memory-leak-with-java">all the ways your application or another component may be leaking memory</a>.</p> <p>All JVM's have pretty good tools for diagnosing memory leaks. Threads like <a href="https://stackoverflow.com/questions/1473510/general-strategy-to-resolve-java-memory-leak">this</a> discuss great ways to find out what is going on.</p> <p><strong>Edit:</strong> some more thoughts</p> <p>You might want to check your configuration for too many sessions if a lot of requests are using <code>HttpServletRequest.getSession()</code>. The <a href="http://tomcat.apache.org/tomcat-7.0-doc/config/manager.html" rel="nofollow noreferrer">Manager</a> component config goes inside <a href="http://tomcat.apache.org/tomcat-7.0-doc/config/context.html" rel="nofollow noreferrer">Context</a> and defaults to -1 for unlimited sessions. </p> <p>Check your version of tomcat with <a href="http://tomcat.apache.org/tomcat-7.0-doc/changelog.html" rel="nofollow noreferrer">the current issue fix list</a> in case you are encountering a known memory leak. </p> <p>Lastly, Tomcat 7 includes a <a href="http://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html#JRE_Memory_Leak_Prevention_Listener_-_org.apache.catalina.core.JreMemoryLeakPreventionListener" rel="nofollow noreferrer">JreMemoryLeakPreventionListener</a> that might show resources not being released. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload