cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

ThingWorx Navigate is now Windchill Navigate Learn More

Translate the entire conversation x

AzureSQL Thingworx Connectivity - CRITICAL ERROR ON STARTUP

pshashipreetham
18-Opal

AzureSQL Thingworx Connectivity - CRITICAL ERROR ON STARTUP

Hi, 

 

I am trying to connect an Azure SQL Managed Instance database to ThingWorx. I can connect the db using the creds from platform-settings.json in SQL Server Management Studio(SSMS)., but when I try to communicate through Thingworx, I get the following error:

2025-07-22 00:07:54.104-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#4] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@48f7f91b -- 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: 
2025-07-22 00:07:54.104-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#7] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@3792a8c8 -- 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: 
2025-07-22 00:07:54.104-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#3] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@49120f7d -- 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: 
2025-07-22 00:07:54.104-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#1] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@75a08dcf -- 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: 
2025-07-22 00:07:54.104-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#0] com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@59579a88 -- 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: 
2025-07-22 00:07:54.107-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#7] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@fe86afe is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-22 00:07:54.108-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#0] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@fe86afe is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-22 00:07:54.108-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#1] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@fe86afe is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-22 00:07:54.108-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#3] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@fe86afe is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-22 00:07:54.108-0700 [L: WARN] [O: c.m.v.r.BasicResourcePool] [I: ] [U: ] [S: ] [P: ] [T: C3P0PooledConnectionPoolManager[identityToken->2x11jfbcdl16egl4oi68|5dde2be7]-HelperThread-#4] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@fe86afe is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2025-07-22 00:07:54.110-0700 [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [P: ] [T: main] *** CRITICAL ERROR ON STARTUP: Connections could not be acquired from the underlying database!

 

This is how platform-settings.json looks:

pshashipreetham_0-1753168490649.png

 

The Thingworx Version of the Upgrade is 10.0

 

Thanks, 

Shashi Preetham,
+91 8099838001 | shashi@psptechhub.com,
PSPTechHub  ||  World of PTC Thingworx  ||  LinkedIn
ACCEPTED SOLUTION

Accepted Solutions

Hi, 

 

The issue is solved. I have followed a video from the PTC itself, which was buried in the Help Centre, and that helped me move forward from this error. 

 

Video Link: 10 FAQs on ThingWorx with Azure SQL - PTC Community

 

Thanks,

Shashi Preetham,
+91 8099838001 | shashi@psptechhub.com,
PSPTechHub  ||  World of PTC Thingworx  ||  LinkedIn

View solution in original post

5 REPLIES 5

Did you setup the DB with the proper scripts?

maybe related (but not Azure): https://community.ptc.com/t5/ThingWorx-Developers/not-able-to-connect-to-thingworx-server/td-p/745295 

https://www.ptc.com/en/support/article/CS285545

https://www.ptc.com/en/support/article/CS312127

 

Also check if you want to set more relaxed parameters in platform-settings, see section persistence providers -> MssqlPersistenceProviderPackage

Hi @Rocko ,

 

Thanks for sharing the articles. I have already gone through them. With the help of an article, I have created a persistence log in Apache. When going through the log, I continuously see an error:

java.sql.SQLException: No suitable driver

 

Attached is the log.

 

Thanks

Shashi Preetham,
+91 8099838001 | shashi@psptechhub.com,
PSPTechHub  ||  World of PTC Thingworx  ||  LinkedIn

"no suitable driver" means something is wrong in your setup. Check which driver jar is used, and that there are no conflicts in the classpath. Also that no extension brings in a different jar. 

Then, make sure it's the right driverclass you refer to, the classname should be in the driverpackage being used.

 

And just to make sure: TWX for AzureSQL is a different download than TWX for MS SQL, I hope you noticed.

Hi @pshashipreetham,
 
I wanted to follow up with you on your post to see if your question has been answered.
If so, please mark the appropriate reply as the Accepted Solution for the benefit of other members who may have the same question.
Of course, if you have more to share on your issue, please let the Community know so that we can continue to support.

Thanks,
Abhi

 

Hi, 

 

The issue is solved. I have followed a video from the PTC itself, which was buried in the Help Centre, and that helped me move forward from this error. 

 

Video Link: 10 FAQs on ThingWorx with Azure SQL - PTC Community

 

Thanks,

Shashi Preetham,
+91 8099838001 | shashi@psptechhub.com,
PSPTechHub  ||  World of PTC Thingworx  ||  LinkedIn
Announcements


Top Tags