Skip to content
This version of SonarQube Server is no longer receiving patches. Please see the latest release for details on updating.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Database-related issues

Troubleshooting database-related issues in SonarQube Server 2025.3.

For AI agents: You're in the SonarQube Server 2025.3 documentation. SonarQube Server 2025.3 is no longer patched. To get patches, upgrade to the latest version. For a list of all 2025.3 pages, see the SonarQube Server 2025.3 page index. For the whole site, see the page index or the full text. For another version, replace 2025.3 in the URL with that version. The latest version has no version number in its URL.

We recommend reading the Server logs first.

Timeout issues when setting up Database Connection Pool

In some configurations when there is a firewall between SonarQube Server and the data you may experience timeout issues. The firewall may interrupt idle DB connections after a specific timeout which can lead to resetting connections. See also Issues with MS SQL Server connection below.

You can customize the HikariCP settings to the defaults listed below to avoid timeout isssues.

sonar.jdbc.idleTimeout=600000
sonar.jdbc.keepaliveTime=300000
sonar.jdbc.maxLifetime=1800000
sonar.jdbc.validationTimeout=5000

Additionally, it is now possible to configure HikariCP properties described here using the following naming convention: sonar.jdbc.{HikariCP property name}.

Issues with MS SQL Server connection

HikariCP may get exhausted from connections causing SonarQube Server to be unresponsive. In this case, the error may display something like HikariPool-1 - Connection is not available or HikariPool-1 - Cannot acquire connection from data source.

In this case, customize the HikariCP settings as follows:

sonar.jdbc.minIdle=25
sonar.jdbc.maxActive=25
sonar.jdbc.maxLifetime=0
sonar.jdbc.maxWait=30000

Oracle JDBC driver blocked

See If using an Oracle database for more information.

Connectivity issue between SonarQube Server and MS SQL Server

If the TCP/IP connection is refused, make sure that Named Pipes and TCP/IP connections are enabled on your SQL Server.

Duplicate keys during background task processing after upgrading to RHEL 8

If you performed an in-place OS upgrade to RHEL 8 or with any similar operating systems and you use PostgreSQL, the new version of glibc may affect locale data changes.

To prevent this, avoid in-place OS upgrades and perform dump-and-restore of the database to an already-upgraded OS.

To correct the issue, restore from a known good backup copy of the database and perform the maintenance steps:

Last updated

Was this helpful?