You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In our logs, we have been receiving the error of
WARN ServiceRunner [c.a.jira.ofbiz.ConnectionPoolHealthSqlInterceptor] Dangerous use of multiple connections: taken => count=2; marks=[1-0]; pool=98/40
Our database server allows for 500 concurrent connections while our jira only allows for 40. Is there any danger to increasing it to a random large number, or can it be set to anything like 100? Thank you!
Technically from the purely database side, meh, doesn't matter, your database is happy with 500, Jira could be configured to use 500. Worst case is that the database using application (Jira in this case) might be coded to thrash the database connections and impose too high a load, so everything ends up too slow. But that would be preventable by just dropping the limit back down.
On the Jira side though, the question is different. What are you doing that makes you think you need more than 40 connections in the pool? What problem are you trying to solve by looking at this?