Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How many database connections should we configure jira to allow?

rj pisciotta
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 17, 2021

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!

1 answer

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 17, 2021

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?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events