Errors in catalina.out when starting KMS running on Apache Tomcat
Originally Published: 2006-12-09
Article Number
Applies To
Microsoft Windows 2003 Server SP1
Apache Tomcat 5.5.20
Sun Java Runtime Environment (JRE) 1.5.0
Issue
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run
WARNING: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1f0aecc -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
Nov 29, 2006 10:04:33 AM com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run
WARNING: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1f0aecc -- APPARENT DEADLOCK!!! Complete Status:
Managed Threads: 3
Active Threads: 3
Active Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1cebc9f (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1c1ac46 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1557c0 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
Pending Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1342a67
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1cbda0a
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@57ea52
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1d8d39f
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@2d95b3
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@bf5555
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@17b4703
Pool thread stack traces:
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1745)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,main]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1745)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]
java.lang.Thread.sleep(Native Method)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1745)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
WARN com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 com.mchange.v2.resourcepool.BasicResourcePool - com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1735f84 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
...
Resolution
Add the following line to the "jdbc/keystore" AND "jdbc/datastore" configuration blocks
automaticTestTable="KMSTestTable_DoNotDelete"
Restart Apache Tomcat
As an example, this would be an RKM Server 2.7 KMS.xml:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/KMS" docBase="KMS" debug="5" reloadable="true" crossContext="true">
<Resource name="jdbc/rkm" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
automaticTestTable="KMSTestTable_DoNotDelete"
connectionCachingEnabled="true"
connectionCacheProperties="{InactivityTimeout=200,AbandonedConnectionTimeout=200,PropertyCheckInterval=30}"
connectionCacheName="KmsConPool"
url="jdbc:oracle:thin:@rkm_db_host:1521:SMRKM"
user="local"
password="-THIS-SHOULD-BE-IGNORED-"
/>
</Context>
Notes
If provided, c3p0 will create an empty table of the specified name, and use queries against that table to test the Connection. If automaticTestTable is provided, c3p0 will generate its own test query, therefore any preferredTestQuery set will be ignored. You should not work with the named table after c3p0 creates it; it should be strictly for c3p0's use in testing your Connection.
Related Articles
Multiple Apache Tomcat Vulnerabilities in RSA Authentication Manager - False Positive Number of Views After starting AFX, some AFX Connectors fail to go to a Running state due to Out of Memory errors in RSA Identity Governan… Number of Views 'The RSA Identity Governance & Lifecycle server is not running and is not in a starting state' when starting RSA Identity … Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' Number of Views AFX Server Fails to Start with 'Could Not Build a Validated Path' and 'Timed Out Waiting for AFX Applications to Start' in… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme…
Don't see what you're looking for?
