Hi,
Yes. SonarQube keeps / thinks the connections are open far longer and continues to try to use them even after your firewall has killed them.
Yep. That means you now have the ability to customize some values. It would be a fair observation, though, to point out that the ticket doesn’t have any details about how to do that customization. I’ve asked for those details. And in the meantime, I tracked down the relevant commit.
It looks like there are new settings for your $SONARQUBE-HOME/conf/sonar.properties file:
sonar.jdbc.idleTimeout, default 600000
sonar.jdbc.keepaliveTime, default 300000
sonar.jdbc.maxLifetime, default 1800000
sonar.jdbc.validationTimeout, default 5000
HTH,
Ann