On 09/12/2009 08:57, Hadole, Nishant IN BOM SISL wrote:
Not sure whether this is applicable here... but encountered similar issue with
Tomcat and XAPOOL...
When DB server fails, connection pool has maximum connection initialised (but
not working). Thus with restart of DB server, Tomcat need to be restarted to
initialize active connections of pool, as this was configured in start-up code.
So, both complaints are basically that you've used all of the resources
available to the server?
Fiddling with Tomcat config is likely to offer you limited success in
improving matters, it's just delaying the same problem appearing later.
You need to increase the resources available, add more servers,
processors or memory - depending on the specific profile of your
application and architecture.
You may make be able to make some performance improvements by tweaking
your application, SQL queries, and the connection pool settings, e.g.
clear out dead connections, test on borrow, test on replace.
These are not Tomcat configuration problems, but if you are lucky you
may attract some guidance from interested parties on this list.
Or you might not.
p
With best regards,
Nishant Hadole
-----Original Message-----
From: Peter Chen [mailto:peter.c...@aicent.com]
Sent: Wednesday, 09 December, 2009 12:36 PM
To: users@tomcat.apache.org
Subject: About the problem "Task
com.mchange.v2.resourcepool.basicresourcepool$acquiret...@1386abc (in deadlocked
PoolThread) failed to complete in maximum time 60000ms. Trying interrupt()."
I deployed my application to the Tomcat 5.5.26. I use hibernate for
O/RM, and the connection pool is c3p0, the database is MySql 5.0.
Several days ago, the Database Server is down, but there are lots of
user accessing the Tomcat.
After I restarted the Database Server, the Tomcat can't connect to the
Database Server automatically.
And I have to restart the Tomcat manually. And only it was restarted,
the Tomcat can connect to the Database Server.
I checked logs, and found that there are lots of Select Operations in
the log file, and there are some error about "deadlocked PoolThread".
Does someone meet this problem before, and what's reason? Thanks.
PS: the content of the log file:
DEBUG 20091207 00:00:30,757>>>>>>>>SELECT * FROM conTable WHERE Keyword
= '172486' AND (Recip = '6590607447' OR Recip like
'6590607447/type=t...@%' )
DEBUG 20091207 00:00:31,815>>>>>>>>SELECT * FROM conTable WHERE Keyword
= '605747' AND (Recip = '6707468443' OR Recip like
'6707468443/type=t...@%' )
.............
DEBUG 20091207 00:00:35,813>>>>>>>>SELECT * FROM conTable WHERE Keyword
= '172486' AND (Recip = '6590607447' OR Recip like
'6590607447/type=t...@%' )
;;;;;;;;;;;;;;;;;
DEBUG 20091207 00:00:36,334>>>>>>>>SELECT * FROM conTable WHERE Keyword
= '160564' AND (Recip = '525510099023' OR Recip like
'525510099023/type=t...@%' )
WARN 20091207 00:00:39,282 Task
com.mchange.v2.resourcepool.basicresourcepool$acquiret...@13ba7d (in
deadlocked PoolThread) failed to complete in maximum time 60000ms.
Trying interrupt().
WARN 20091207 00:00:39,282 Task
com.mchange.v2.resourcepool.basicresourcepool$acquiret...@1386abc (in
deadlocked PoolThread) failed to complete in maximum time 60000ms.
Trying interrupt().
WARN 20091207 00:00:39,282 Task
com.mchange.v2.resourcepool.basicresourcepool$acquiret...@e78f88 (in
deadlocked PoolThread) failed to complete in maximum time 60000ms.
Trying interrupt().
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
