Same issue here!
openjdk version “17.0.10” 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-120.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-120.04.1, mixed mode, sharing)
- Community Edition
- v10.5.1 (90531)
Dear All,
We have the same error since we upgraded from Version 10.0 to 10.5. We also tried to install the 10.5.1 without any change on this issue.
All scan tasks are blocked since this upgrade and we are not anymore able to run any scan from any pipeline systems (Azure DevOps, Jenkins, …).
We are running the 10.5.1 with Community Edition on AKS
We can’t downgrade the version since the upgrade change the Database and we have any pipeline with code review blocked.
Do you have any potential date for the fix availability ?
Thanks by advance
Fab
Hello,
same issue here :
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy
at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:145)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:424)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386)
at ch.qos.logback.classic.Logger.error(Logger.java:543)
at org.eclipse.jgit.internal.util.ShutdownHook.cleanup(ShutdownHook.java:87)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.ThrowableProxy
at java.base/java.net.URLClassLoader.findClass(Unknown Source)
at org.sonarsource.scanner.api.internal.IsolatedClassloader.loadClass(IsolatedClassloader.java:82)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
... 6 more
Execution on a jenkins job with a docker container. We use proxy configuration to join the sonarqube server:
export SONAR_SCANNER_OPTS=-Dhttps.proxyHost=XXXXX.zscaler.net -Dhttps.proxyPort=443
sonar-scanner -X -Dsonar.cfamily.compile-commands=build/linux_desktop/compile_commands.json -Dsonar.sources=app,lib -Dsonar.exclusions=**/*.html,**/*.css,**/*.js,**/*.ts
SonarScanner 5.0.1.3006
Java 17.0.7 Eclipse Adoptium (64-bit)
Linux 5.4.0-174-generic amd64
Sonarqube Enterprise : 10.5.0 (89998)
Hi folks,
We are aware of this annoying INFO log, but to our knowledge, it is not failing the analysis. The scanner process’s exit code should be “0.”
Does anyone know why this is making your pipelines fail? Do you have any special log parsing feature in place maybe?
This is to be sure we have a full understanding of the issue and fix it accordingly.
Thanks
Don’t be confused by the class name ThrowableProxy. This has nothing to do with HTTP proxy.
Given only that stack trace, your error is not related to this issue: you must define sonar.projectKey somehow.
Depending on your workflow it could be manual or automatic.
1 Like
Any news about it?
Thanks!
I don’t think there is a relation between the first exception (again, it’s just a too verbose log; the analysis is successful) and the following error.
Looks like you have a Groovy step running in your pipeline, and this one is failing.
Our Gitlab Pipeline failed too, however, the issue described in this thread was not the root cause that led to the pipeline failure. So this seems to be an “cosmetic” issue only.
1 Like
cosmetic or not should be solved, i h’ve used the 9.8 version without any problems.
I received the following error while scanning code on my local Ubuntu machine and on the Gitlab pipeline.
Soanrqube server version : sonarqube:10.5.0-community
Sonar scanner version : sonar-scanner-cli:5.0.1 - also tested with latest version.
This is a major blocker as it causes the coverage result not to be picked up by SonarScanner.
macOS M1 self-hosted agent using Java 17 and Azure DevOps
INFO: ------------------------------------------------------------------------
##[error]Exception in thread "Thread-0" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy
at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:145)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:424)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386)
at ch.qos.logback.classic.Logger.error(Logger.java:543)
at org.eclipse.jgit.internal.util.ShutdownHook.cleanup(ShutdownHook.java:87)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.ThrowableProxy
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy
at ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:145)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:424)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386)
at ch.qos.logback.classic.Logger.error(Logger.java:543)
at org.eclipse.jgit.internal.util.ShutdownHook.cleanup(ShutdownHook.java:87)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.ThrowableProxy
##[error]... 6 more
... 6 more
The SonarScanner CLI has finished
06:14:57.99 Post-processing succeeded.
Finishing: SonarQubeAnalyze
@Amir as noted above:
I also encountered the same problem, do not know how to solve,using Java 17 ,
sonar-scanner-5.0.1.3006-windows and sonarqube-developer-10.5.1.90531
I have the same problem as you. Have you solved it
Hi
This is being addressed and should be fixed in the next release
Thanks
2 Likes
Thanks for your information, it would be great to know the release date of the next version.
Hi,
you may track the development of Sonarqube via Jira JQL
project = SonarQube AND fixVersion = <version> AND status != Closed
Gilbert
1 Like
Hello,
I update to 10.5.1 with Azure pipeline build and have the same error