Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 593
  • Last Modified:

Errororg.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object

what is the cause of this error?
0
Dehankar
Asked:
Dehankar
  • 2
1 Solution
 
rama_krishna580Commented:
Check that the setting for the maximum number of connections in the pool is adequate.

I would highly recommend /against/ "no limit" connection pools. Even if you try set the connection pool size to be the same as the request handler pool size (which should be equivalent a long as you don't have DB connection leaks), you shouldn't set it to "no limit". You could bring down your database server if you have a connection leak on an app server. It's best to set your limit to something reasonable, but firm.

--> Setting the maxactive other than 0 and your problem will be solved....

R.K
0
 
DehankarAuthor Commented:
thanks
0
 
DehankarAuthor Commented:
thanks
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now