Skip to main content
V
VG_83231554-Participant
4-Participant
November 20, 2023
Question

Can we set max pool size to 300 in ThingWorx 9.0?

  • November 20, 2023
  • 2 replies
  • 1042 views

We are getting "SQL Query Failed" error from last couple of days.

Error details- Execute Query Failed: java.sql.SQLException: Cannot get a connection, pool error Timeout waiting for idle object

 

Currently, We have set max pool size to 200. Want to understand following things

1. Can we set it to 300?

2. What factor we should consider before increasing pool size?

3. Does this will impact on my other application which also access the same DB?

 

We are using ThingWorx 9.0 with SQL Server

 

Thanks

2 replies

P
PaiChung22-Sapphire I
22-Sapphire I
November 20, 2023

A DB Server based on what type it is will be able to accommodate a number of connections.

Standard MS SQL server can support a total of 30K connections

If you are using Azure SQL please double check, because it might be based on SKU

So yes you should be able to increase that number.

Please note that if you are using PostGreSQL there are much lower limits especially in Azure PostGres Single Server (vs. Flex which supports 5K)

S
slangleyCommunity Manager
Community Manager
December 22, 2023

Hi @VG_8323155.

 

To tack on to Pai's response, you also need to make sure your server is sized to support any config changes.  You do need to be mindful in a shared database server to ensure it doesn't exceed the total number of connections supported by the database.  If you are subscribing to database services via Azure, etc. you may have to update the tier to allow for more connections.

 

Regards.

 

--Sharon

Terms & ConditionsAccessibility statement