Jira connection Pool Graph Not Reflecting DBConfig.xml

[Jason Abergel]

Hi All,

We recently updated our Pool Max Size and Pool Max Idle from the default of 20 to 60 to account for plugin and user growth. Below is how I configured it, is this the recommended way to configure this with all 3 configured with the same value?

<pool-min-size>60</pool-min-size>
<pool-max-size>60</pool-max-size>
<pool-max-idle>60</pool-max-idle>

[Shaun S · Accepted solution]

Hi Jason,

Configuring the pool-min-size and pool-max-size values with the same number is generally the recommended way of doing things. Since the minimum and maximum pool size is the same, the pool-max-idle setting is ignored as they aren't applicable. In short, I don't see any reason why the settings you provided would be an issue. The database monitoring graph can take a few minutes for the new pool size settings to be visible. In order for JIRA to apply the changes to the pool size, the service needs to be restarted. After making the changes to dbconfig.xml did you restart the Jira service?

[Jason Abergel]

Hi Shaun,

Ok thanks, that's what I figured but it is nice to have it confirmed.

Yes, the service was restarted and I was able to see the graph shortly after.

Thanks for your time in taking a look at this.

Cheers!

[Shaun S]

Happy to help!  I'm glad restarting the service cleared things up.