It was for the users of org.apache.cayenne.conf.WebApplicationContextFilter. If
an app bootstraps Cayenne on its own, I would suggest emulating this filter's
"destroy" method in an appropriate servlet or filter:
public void destroy() {
Configuration config = Configuration.getSharedConfiguration();
if (config != null) {
config.shutdown();
}
}
Andrus
On Oct 28, 2010, at 4:23 PM, Michael Gentry wrote:
> I believe this was fixed in 3.0.1.
>
> On Thu, Oct 28, 2010 at 7:31 AM, Bruno René Santos <[email protected]> wrote:
>> Also when i undeploy a portlet with cayenne embedded on it i get the error
>>
>> SEVERE: A web application appears to have started a thread named
>> [cayenne-edt-2855942-4] but has failed to stop it. This is very likely to
>> create
>> a memory leak.
>>
>> 28/Out/2010 12:29:56 org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads
>>
>> Several times, which also means, I think, that the connection is on.
>>
>>
>>
>> Thanx
>>
>>
