Error Starting Sonarqube after upgrade to 2025.1.1

SonarQube Server / Community Build
,
1

We have been running Sonarqube 10.6 connecting to Azure SQL using managed identity. My connection string looks similar to:

sonar.jdbc.url=jdbc:sqlserver://#######.database.###cloudapi.net:1433;database=sonar;encrypt=true;trustServerCertificate=false;loginTimeout=30;Authentication=ActiveDirectoryMSI

We get the following error when starting the service:

> 2025.03.19 16:56:28 WARN  web[][o.s.c.a.AnnotationConfigApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@659e0bfd-org.sonar.db.DefaultDatabase': com/azure/identity/ManagedIdentityCredential
> 2025.03.19 16:56:28 ERROR web[][o.s.s.p.w.PlatformServletContextListener] Web server startup failed
> org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@659e0bfd-org.sonar.db.DefaultDatabase': com/azure/identity/ManagedIdentityCredential
> 
> Caused by: java.lang.ClassNotFoundException: com.azure.identity.ManagedIdentityCredential

Any assistance is appreciated. Note, service is using the local service and a managed identity for the host server has a login on the database, same as prior to upgrade.

2

Hi,

I’m a bit confused. First you say you “have been running” 10.6 and then you mention an upgrade.

So were you successfully running 10.6 and then this error suddenly started happening? Or did you recently upgrade to 10.6 and encounter this error?

If the former, then you’ll need to look external to SonarQube to find the source of this problem.

 
Ann

3

Sorry if this wasn’t clear. We were running version 10.6 and upgraded to 2025.1.1. However, when starting services, we initially got jdbc errors, not able to connect to SQL (Azure SQL). In the interim, we looked closer and realized we didn’t have the correct JDBC files. Seems that putting the jdbc jar and dll in path, we were finally able to get services communicating with Azure SQL and we are now up. I can add more specifics before closing this topic. The key is getting the proper jdbc for the installation.

1 Like