-->
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.  [ 4 posts ] 
Author Message
 Post subject: c3p0 apparent deadlock / creating emergency threads
PostPosted: Mon Jul 05, 2010 1:24 pm 
Newbie

Joined: Mon Jul 05, 2010 1:17 pm
Posts: 4
Hi Guys,

i found this thread here in this forum.. but it doenst seem to have a solution for the issue:
viewtopic.php?t=947246&highlight=apparent+deadlock+c3p0

I am still getting the errors under high load. Every few hours hour server is bringing up this error message. we are using:

Code:
hibernate-core-3.3.1.GA.jar
hibernate-c3p0-3.3.1.GA.jar
hibernate-3.2.6.ga.jar
c3p0-0.9.1.2.jar


i tried already to set max_statements to 0 and to a very high number 30.000 (because its only DB server - so it can take all the RAM)... both didnt work. any solutions on that?

Exact errormessage is:

Code:
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@7030f9f0 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!  [com.mchange.v2.async.ThreadPoolAsynchronousRunner]


I am really lost with this problem.

Thank you for your help guys.
Thomas


Top
 Profile  
 
 Post subject: Re: c3p0 apparent deadlock / creating emergency threads
PostPosted: Tue Jul 06, 2010 3:34 am 
Newbie

Joined: Mon Jul 05, 2010 1:17 pm
Posts: 4
Hey hey, nobody has an Idea?

heres our hibernate.properties and our my.cfn

Code:
jdbc.driverClassName=com.mysql.jdbc.Driver
jdbc.url=jdbc:mysql://***/***?useUnicode=true&characterEncoding=UTF-8
jdbc.username=***
jdbc.password=***

hibernate.dialect=org.hibernate.dialect.MySQL5InnoDBDialect
hibernate.show_sql=false
hibernate.connection.charSet=utf8
hibernate.update.mode=update

hibernate.c3p0.minPoolSize=5
hibernate.c3p0.maxPoolSize=400
hibernate.c3p0.timeout=1000
hibernate.c3p0.max_statement=300

hibernate.cache.provider_class=org.hibernate.cache.EhCacheProvider
hibernate.cache.region_prefix=hibernate
hibernate.cache.use_second_level_cache=true
hibernate.cache.use_query_cache=true



Code:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port      = 3306
socket      = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket      = /var/run/mysqld/mysqld.sock
nice      = 0

[mysqld]
#
# * Basic Settings
#
user      = mysql
pid-file   = /var/run/mysqld/mysqld.pid
socket      = /var/run/mysqld/mysqld.sock
port      = 3306
basedir      = /usr
datadir      = /var/lib/mysql
tmpdir      = /tmp
language   = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address      = 127.0.0.1
#
# * Fine Tuning
#
key_buffer      = 16M
max_allowed_packet   = 16M
thread_stack      = 128K
thread_cache_size   = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover      = BACKUP
max_connections         = 30000
table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log      = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
log_slow_queries   = /var/log/mysql/mysql-slow.log
long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id      = 1
#log_bin         = /var/log/mysql/mysql-bin.log
expire_logs_days   = 10
max_binlog_size         = 100M
#binlog_do_db      = include_database_name
#binlog_ignore_db   = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet   = 16M

[mysql]
#no-auto-rehash   # faster start of mysql but no tab completition

[isamchk]
key_buffer      = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1


#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/


Top
 Profile  
 
 Post subject: Re: c3p0 apparent deadlock / creating emergency threads
PostPosted: Tue Jul 06, 2010 8:42 am 
Newbie

Joined: Mon Jul 05, 2010 1:17 pm
Posts: 4
i am also willing to pay for it if somebody can offer help here..


Top
 Profile  
 
 Post subject: Re: c3p0 apparent deadlock / creating emergency threads
PostPosted: Tue Dec 10, 2013 11:30 am 
Newbie

Joined: Mon Oct 28, 2013 2:24 pm
Posts: 2
twago wrote:
i am also willing to pay for it if somebody can offer help here..


hi, have you managed to solve this issue? it seems we are facing something similar.


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

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.