On 25/06/2019 12:58, Christoph Hanke wrote: > Hi, > > I have got a jspx Page which gets reloaded every 30 seconds to show some > status information. Consequently there are database requests every 30 > seconds. Before switching from glassfish to tomcat (7.0.94) there were > no issues with that, but now the memory consumption is bloating over time. > > Looking at the heapdump I recognized that the the traceLists of the used > preparedStatements and the resultSets are the cause of the memory > consumption. > > I already tried to use***removeAbandoned*=true and > setting*removeAbandonedTimeout=5 *seconds, as well as turning off my > jspx-database-requests over night, thinking this could provide the > necessary "timeout" for the connection / AbandonedTrace objects ( > https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/tomcat/dbcp/dbcp/AbandonedTrace.html > ) to get cleaned up. Unfortuneatly it did not. I'm now thinking to turn > of the tracking (by using |*clearTrace > <https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/tomcat/dbcp/dbcp/AbandonedTrace.html#clearTrace()>*()| > ) but it seems a little bit hackish to me. Has someone eventually an > idea where to look at or what to do?
Do the logs indicate you have a connection leak? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
