Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,659
Community Members
 
Community Events
176
Community Groups

How many database connections should we configure jira to allow?

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

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

Atlassian Community Events