[c3p0-users] C3P0Registry mbean is already registered - on redeploy
Status: Beta
Brought to you by:
swaldman
From: Tom E. <ro...@te...> - 2007-06-28 14:17:24
|
Hello, I am using c3p0 v0.9.1.1 in a Tomcat 5.5.23 with Hibernate 3.2.2. I do not have full access to the Tomcat, i.e. I can only copy a war of my application to the webapps dir, causing a Tomcat redeploy. When I do that, I get a lot of messages like the following: 2007-06-16 15:43:28,933 1232 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] WARN com.mchange.v2.c3p0.management.ActiveManagementCoordinator - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources. I am sure that my Application calls (Hibernate) SessionFactory.close() upon redeploy. That is all I am supposed to do, right ? Now, is this an indication of a real problem (memory leak), or should I just disable the JMX stuff, as I am not using it. Thanks & Kind regards, Tom. |