Article - CS321828
Unable to initialize and start ThingWorx after upgrade: Connections could not be acquired from the underlying database
Modified: 09-Jul-2021
Applies To
- ThingWorx Platform 8.3 SP4 to SP13
- ThingWorx Platform 8.5 F000
Description
- Unable to access ThingWorx application, error reported in in Application.log:
- Error "[L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] [message: Unable to initialize and start system: Connections could not be acquired from the underlying database!]
- ThingWorx fails to connect with Azure PostgreSQL when SSL is enabled
- ThingWorx upgrade 8.3.2 to 8.3.13 fails with database errors
- [T: C3P0PooledConnectionPoolManager[identityToken->2zrp6taacn6g9q13pprtf|629b4152]-HelperThread-#0] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@36ff7d0a -- 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 (3). Last acquisition attempt exception:
- ThingWorx failes to connect Azuere PostgreSQL when using SSO
- [T: C3P0PooledConnectionPoolManager[identityToken->]-HelperThread-#0] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@7b02740 -- 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:
[T: C3P0PooledConnectionPoolManager[identityToken->]-HelperThread-#0] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@50501608 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
- [T: C3P0PooledConnectionPoolManager[identityToken->]-HelperThread-#0] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@7b02740 -- 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:
This is a printer-friendly version of Article 321828 and may be out of date. For the latest version click CS321828