Cannot get a connection, pool error Timeout waiting for idle object | Community
Skip to main content
S
SebasRios
June 22, 2021
Solved

Cannot get a connection, pool error Timeout waiting for idle object

  • June 22, 2021
  • 1 reply
  • 18151 views

Hello everyone,

 

We are having an issue with our JDBC connection pool on the Manager Web Console
Configuration. We have created several custom workflow components that access a SQL Server Database and perform updates and inserts to the database. 

When it reaches the third component (Bulk Update Part 3), it triggers the following error: Cannot get a connection, pool error Timeout waiting for idle object, but it works just fine with the other two.

 

I was able to find this article on how to create a DataSourcePool: http://scottsdigitalcommunity.blogspot.com/2013/09/injecting-datasourcepool-service-into.html

 

Any ideas what I could change in the data source pool configuration?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Vijayalakshmi_S

Hi @sebasrios,

If you are closing the connections upon usage correctly in other process components/wherever it is used and in need to additional connections through the connection pool,

  • You can increase the number of connections (Pool size - highlighted in red) in your respective OSGI factory config instance. 

If you are sure that the available number of connections is suffice(you already have greater number on Pool size based on the need) but still the timeout error is observed,

  • Increase the wait time (Pool wait - highlighted in green)

1 reply

Vijayalakshmi_S
Vijayalakshmi_SAccepted solution
June 22, 2021

Hi @sebasrios,

If you are closing the connections upon usage correctly in other process components/wherever it is used and in need to additional connections through the connection pool,

  • You can increase the number of connections (Pool size - highlighted in red) in your respective OSGI factory config instance. 

If you are sure that the available number of connections is suffice(you already have greater number on Pool size based on the need) but still the timeout error is observed,

  • Increase the wait time (Pool wait - highlighted in green)

    S
    SebasRiosAuthor
    June 28, 2021
    Thank you very much! We were closing the connection pool incorrectly, nonetheless the pool size and pool wait helped us a lot!
    Terms & ConditionsAccessibility statement

    Loading footer...