Unable to load component class org.sonar.scanner.report.ActiveRulesPublisher - After profile updates

Hello Team,

We are getting below error in the Jenkins pipeline during Sonarqube scanning. (task :sonarqube in gradle)

Unable to load component class org.sonar.scanner.report.ActiveRulesPublisher

19:51:33 > Task :sonarqube FAILED
19:51:33 FAILURE: Build failed with an exception.
19:51:33 * What went wrong:
19:51:33 Execution failed for task ':sonarqube'.
19:51:33 > Unable to load component class org.sonar.scanner.report.ActiveRulesPublisher
19:51:33 * Try:
19:51:33 Run with --info or --debug option to get more log output. Run with --scan to get full insights.
19:51:33 * Exception is:
19:51:33 org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':sonarqube'.

We cleared the indexes by deleting the es6 directory, however, this is happening almost daily and we do not want to get into the solution of deleting the directory everyday.

This issue is related to profile updates (specifically, to a profile with a child profile). These were system updates, not user triggered.

Is there any other better solution for this?

Versions: Sonarqube 7.9.2 Developer Edition, SonarJava plugin 6.3.2 (same issue with 5.13.1 as well)

  • what are you trying to achieve:
    We have a Jenkins pipeline that does a gradle build with tasks “bootJar test sonarqube”. We have observed that this happens when profiles are updated, and these were system updates not user ones
  • what have you tried so far to achieve this:
    Deleting the contents of es6 directory under /sonar/data solves this issue but it comes back up whenever the profiles are updated.

Hello Omkar,

This error may be related to ElasticSearch gracefully failing some API calls when disk space is low (space usage is above 85%). Please check this thread: Initial setup integration failing

See the last reply in that thread and check your disk usage, whether it is above or below the 85% mark. You may need to free up some space.

Best regards,

Hello Daniel,

Thanks a lot for the quick response. We have lots of free space on the disk, so that is not the issue. Whenever there’s a update to the profile, this issue is coming up. We just now faced this issue again and it was due to profile updates.


Can you get gradle to display a full stack trace? Try running it with -d -s.