-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: c3p0 apparent deadlock / creating emergency threads
PostPosted: Sat Jul 16, 2011 4:33 pm 
Newbie

Joined: Sat Jul 16, 2011 4:15 pm
Posts: 3
Versions:
Hibernate 3
c3p0-0.9.1

I was using it @ my own computer with eclipse and it works perfectly.
When I tryed to send all my applications to linux red/hat, the problems begin.

I'm getting messages such as the following:

When I stop tomcat:
Code:
INFO: Stopping service Catalina
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/gefin] 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.
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/gefin] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/gefin] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/gefin] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/gefin] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:56 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/gefin] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/direc] 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.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/direc] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Jul 16, 2011 5:24:56 PM org.apache.coyote.http11.Http11Protocol destroy


and when I start tomcat:
Code:
WARNING: 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.
....
WARNING: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@14f2bd7 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
Jul 16, 2011 5:29:25 PM com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run
WARNING: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@14f2bd7 -- APPARENT DEADLOCK!!! Complete Status:
        Managed Threads: 3
        Active Threads: 3
        Active Tasks:


My hibernate.properties c3p0 lines:
<property name="c3p0.acquire_increment">1</property>
<property name="c3p0.idle_test_period">10</property> <!-- seconds -->
<property name="c3p0.max_size">50</property>
<property name="c3p0.max_statements">0</property>
<property name="c3p0.min_size">5</property>
<property name="c3p0.timeout">60</property> <!-- seconds -->
<property name="hibernate.c3p0.preferredTestQuery">select 1;</property>


Can you please help me?
Thanks, Ryan


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.