[#PETALSVIEW-17] memory leak message from tomcat - Petals Link JIRA

Details

Type: Improvement Request
Status: Open
Priority: Minor
Resolution: Unresolved
Affects Version/s: 1.2
Fix Version/s: None
Component/s: None
Security Level: Public

Description:

Hide

Every time we stop the tomcat, we've got this message:

GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 File Lock Watchdog /users/petalsgui/test/db/petalsview.lock.db] but has failed to stop it. This is very likely to create a memory leak.
1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 Log Writer PETALSVIEW] but has failed to stop it. This is very likely to create a memory leak.

Is tomcat dummy? I don't think. So maybe there are some thread closings badly implemented...
Put this track as minor?

Show
Every time we stop the tomcat, we've got this message: GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc GRAVE: The web application [/petals-view-ui] registered the JBDC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 File Lock Watchdog /users/petalsgui/test/db/petalsview.lock.db] but has failed to stop it. This is very likely to create a memory leak. 1 oct. 2010 15:09:14 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads GRAVE: The web application [/petals-view-ui] appears to have started a thread named [H2 Log Writer PETALSVIEW] but has failed to stop it. This is very likely to create a memory leak. Is tomcat dummy? I don't think. So maybe there are some thread closings badly implemented... Put this track as minor?

Environment:

tomcat 6, jdk 1.6, RHEL 5

Issue Links

Depends

This issue blocks:
PETALSVIEW-22 C3PO

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

strino added a comment - Mon, 8 Nov 2010 - 15:24:25 +0100

It is a Tomcat bug in its DBCP, you can see the issue https://issues.apache.org/jira/browse/DBCP-332. Tomcat is doing its job right.
Two possible ways :

waiting DBCP correction
using C3PO for connection pool

Show

strino added a comment - Mon, 8 Nov 2010 - 15:24:25 +0100 It is a Tomcat bug in its DBCP, you can see the issue https://issues.apache.org/jira/browse/DBCP-332. Tomcat is doing its job right. Two possible ways :

waiting DBCP correction
using C3PO for connection pool

Petals View

memory leak message from tomcat

Details

Issue Links

Activity

People

Dates