SonarQube 10.4 seems to leak database connections

Hello,

For us it was CE active connections started to grow after 4 hours of upgrade and we had the MaxActive connection set us 60 ( default ). So after the connection count reaches 60, which never happened before, we started to get the error reported here.
As a workaround, we increased the maxActive connection to 600 and now we do not see an abrupt spike in the active connections. But it looks like the connections are slowly growing and are not getting released.
We have the idle_in_transaction_session_timeout set to 5 Minutes. But maxLifeTime connection is default 180000. We are thinking of reducing this to less than 5 minutes.

DB connection status after initial upgrade:

DB connections slowly growing after increasing the maxActive to 600

2 Likes

On our side, it seems that the issue can be detected. Below the grafana logs:

Maybe this status can be leveraged in the helm-chart, as a livenessProbe ?

1 Like

Hi all,

A quick update on the topic:
We’re planning to trigger soon a 10.4.1 bug-fix release to fix the issue.

Chris

4 Likes

hi @Chris ,

Thanks for the quick decision and plan to release bugfix version. How soon we can expect this ?
And is there any workaround we can do until this release ?

Hi there, @C0011264

The patch has already been released. Many thanks for your patience! :slight_smile:

Regards
Alain

4 Likes

Hi.

Will there be a Helm chart for the patch as well? If so, when can we expect it to be available?

Hi @ACarls,

The updated Helm chart for 10.4.1 is available too on ArtifactHub.

Regards,
Matteo

5 Likes