install the enterprise co-ordinator hangs at end when communication with the data base has access to firewall ...sees the port getting changed from 1433 to 1434 firewall will only allow 1434 40222983 06/30/2011 12:00:00 AM
Originally Published: 2010-11-19
Article Number
Applies To
Issue
Installer for Enterprise Manager/Enterprise Co-ordinator hangs, last message in DLPInstall.log is:
"Info: Starting 'TablusEnterpriseManager' service with updated paramater values..."
DLP Enterprise Manager service will not start or remains in state "Starting"
18 Nov 2010 15:19:19,378 | DEBUG - RecoverableDataSource.regenerateDataSource(255) | Regenerating data source; class: com.microsoft.sqlserver.jdbc.SQLServerDriver url: jdbc:sqlserver://BAL-MSQ-48A;instanceName=SQLEXPRESS,1433;sendStringParametersAsUnicode=true;integratedSecurity=true;selectMethod=cursor;encrypt=true;trustServerCertificate=true;databaseName=RSA_DLP_EM; username:
18 Nov 2010 15:19:20,081 | DEBUG - RecoverableDataSource.regenerateDataSource(266) | Initial pool size: 7; idle test period: 120; max pool size: 20
18 Nov 2010 15:19:40,269 | WARN - ThreadPoolAsynchronousRunner$DeadlockDetector.run(608) | com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@56ac7 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
18 Nov 2010 15:19:40,269 | WARN - ThreadPoolAsynchronousRunner$DeadlockDetector.run(624) | com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@56ac7 -- APPARENT DEADLOCK!!! Complete Status:
Managed Threads: 3
Active Threads: 3
Active Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@d6d868 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@119a19c (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1c11082 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
Pending Tasks:
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@22f5dd
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@13bb17a
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@cc80
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@721088
Pool thread stack traces:
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]
java.net.PlainDatagramSocketImpl.receive0(Native Method)
java.net.PlainDatagramSocketImpl.receive(Unknown Source)
java.net.DatagramSocket.receive(Unknown Source)
com.microsoft.sqlserver.jdbc.SQLServerConnection.getInstancePort(SQLServerConnection.java:3148)
com.microsoft.sqlserver.jdbc.SQLServerConnection.primaryPermissionCheck(SQLServerConnection.java:953)
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:816)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]
java.net.PlainDatagramSocketImpl.receive0(Native Method)
java.net.PlainDatagramSocketImpl.receive(Unknown Source)
java.net.DatagramSocket.receive(Unknown Source)
com.microsoft.sqlserver.jdbc.SQLServerConnection.getInstancePort(SQLServerConnection.java:3148)
com.microsoft.sqlserver.jdbc.SQLServerConnection.primaryPermissionCheck(SQLServerConnection.java:953)
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:816)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,main]
java.net.PlainDatagramSocketImpl.receive0(Native Method)
java.net.PlainDatagramSocketImpl.receive(Unknown Source)
java.net.DatagramSocket.receive(Unknown Source)
com.microsoft.sqlserver.jdbc.SQLServerConnection.getInstancePort(SQLServerConnection.java:3148)
com.microsoft.sqlserver.jdbc.SQLServerConnection.primaryPermissionCheck(SQLServerConnection.java:953)
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:816)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
18 Nov 2010 15:20:40,270 | WARN - ThreadPoolAsynchronousRunner.processReplacedThreads(416) | Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@d6d868 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
18 Nov 2010 15:20:40,270 | WARN - ThreadPoolAsynchronousRunner.processReplacedThreads(416) | Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@119a19c (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
18 Nov 2010 15:20:40,270 | WARN - ThreadPoolAsynchronousRunner.processReplacedThreads(416) | Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1c11082 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
Cause
Resolution
The browser service by default will be on UDP port 1434. The jdbc client will connect to this port initially or will connect directly to the port specified in the jdbc url.
i.e. to connect to tcp port 1433:
jdbc:sqlserver://EM_SQL_DB_HOST:1433;
Related Articles
Co-existence of RSA IIS and Apache Agents on the same server 43Number of Views RSA Announces the Release of RSA MFA Agent 9.0 for Microsoft IIS 33Number of Views Prime 101: Prime in Pictures 37Number of Views List of Trusted Certificate Authorities for HFED and Trusted Headers Applications 72Number of Views DELL EMC Avamar Rel19.2 - RSA Ready SecurID Access Implementation Guide 109722 18Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?