cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CAY-1542) DI container is not shutting down Cayenne-managed connection pool
Date Sun, 20 Feb 2011 12:58:38 GMT

     [ https://issues.apache.org/jira/browse/CAY-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrus Adamchik closed CAY-1542.
--------------------------------

    Resolution: Fixed

not handling the DriverManager leak situation - not quite clear what Cayenne should do about
it , as it doesn't know about the scope of a static variable. Besides Tomcat seems to be doing
the right thing, and the warning message it prints is just an FYI.

> DI container is not shutting down Cayenne-managed connection pool
> -----------------------------------------------------------------
>
>                 Key: CAY-1542
>                 URL: https://issues.apache.org/jira/browse/CAY-1542
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.1M2
>         Environment: Tomcat 7.0.8, Cayenne 3.1 - trunk build from 01.30.2011
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>            Priority: Minor
>             Fix For: 3.1M2
>
>
> Tomcat 7 has nice facilities for tracking resource leaks. When shutting down tomcat that
runs a Cayenne webapp similar to our tutorial, with CayenneFilter managing Cayenne resources
and org.apache.cayenne.configuration.server.XMLPoolingDataSourceFactory, I get the following
messages:
> SEVERE: The web application [/fooweb] registered the JDBC driver [com.mysql.jdbc.Driver]
but failed to unregister it when the web application was stopped. To prevent a memory leak,
the JDBC Driver has been forcibly unregistered.
> Feb 19, 2011 12:44:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/fooweb] appears to have started a thread named [PoolManagerCleanup-728981380]
but has failed to stop it. This is very likely to create a memory leak.
> Will need to ensure that DI shutdown propagates to XMLPoolingDataSourceFactory and it
does the right thing.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message