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?
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events