Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
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

Join now to unlock these features and more

How many database connections should we configure jira to allow?

rj pisciotta
rj pisciotta 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!

Answer
Watch
Like Be the first to like this
377 views

1 answer

1 vote
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
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?

Reply

Suggest an answer

Log in or Sign up to answer
Jira Core
Jira Core Server
TAGS
AUG Leaders

Atlassian Community Events

See all events