ClassNotFoundException in the new issue assign mechanism in sonar 5.1

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Jorge Costa
hi guys,

i got this exception and looks to be from the new automatic assign feature in 5.1. The analysis was ok tough, only the post job failed

[04:22:36] : [Step 1/1] INFO: ------------------------------------------------------------------------
[04:22:36] : [Step 1/1] INFO: EXECUTION FAILURE
[04:22:36] : [Step 1/1] INFO: ------------------------------------------------------------------------
[04:22:36] : [Step 1/1] Total time: 14:04.117s
[04:22:36] : [Step 1/1] Final Memory: 55M/746M
[04:22:36]W: [Step 1/1] ERROR: Error during Sonar runner execution
[04:22:36] : [Step 1/1] INFO: ------------------------------------------------------------------------
[04:22:36]W: [Step 1/1] org.sonar.runner.impl.RunnerException: Unable to execute Sonar
[04:22:36]W: [Step 1/1] at org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:91)
[04:22:36]W: [Step 1/1] at org.sonar.runner.impl.BatchLauncher$1.run(BatchLauncher.java:75)
[04:22:36]W: [Step 1/1] at java.security.AccessController.doPrivileged(Native Method)
[04:22:36]W: [Step 1/1] at org.sonar.runner.impl.BatchLauncher.doExecute(BatchLauncher.java:69)
[04:22:36]W: [Step 1/1] at org.sonar.runner.impl.BatchLauncher.execute(BatchLauncher.java:50)
[04:22:36]W: [Step 1/1] at org.sonar.runner.api.EmbeddedRunner.doExecute(EmbeddedRunner.java:102)
[04:22:36]W: [Step 1/1] at org.sonar.runner.api.Runner.execute(Runner.java:90)
[04:22:36]W: [Step 1/1] at org.sonar.runner.Main.executeTask(Main.java:70)
[04:22:36]W: [Step 1/1] at org.sonar.runner.Main.execute(Main.java:59)
[04:22:36]W: [Step 1/1] at org.sonar.runner.Main.main(Main.java:41)
[04:22:36]W: [Step 1/1] Caused by: java.lang.NoClassDefFoundError: org/sonar/core/issue/IssuesBySeverity
[04:22:36]W: [Step 1/1] at org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob.sendNotifications(SendIssueNotificationsPostJob.java:81)
[04:22:36]W: [Step 1/1] at org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob.executeOn(SendIssueNotificationsPostJob.java:59)
[04:22:36]W: [Step 1/1] at org.sonar.batch.phases.PostJobsExecutor.execute(PostJobsExecutor.java:62)
[04:22:36]W: [Step 1/1] at org.sonar.batch.phases.PostJobsExecutor.execute(PostJobsExecutor.java:52)
[04:22:36]W: [Step 1/1] at org.sonar.batch.phases.DatabaseModePhaseExecutor.execute(DatabaseModePhaseExecutor.java:136)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:264)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:235)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:230)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:220)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ScanTask.scan(ScanTask.java:57)
[04:22:36]W: [Step 1/1] at org.sonar.batch.scan.ScanTask.execute(ScanTask.java:45)
[04:22:36]W: [Step 1/1] at org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:135)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W: [Step 1/1] at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W: [Step 1/1] at org.sonar.batch.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:158)
[04:22:36]W: [Step 1/1] at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95)
[04:22:36]W: [Step 1/1] at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67)
[04:22:36]W: [Step 1/1] at org.sonar.runner.batch.IsolatedLauncher.execute(IsolatedLauncher.java:45)
[04:22:36]W: [Step 1/1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[04:22:36]W: [Step 1/1] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[04:22:36]W: [Step 1/1] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[04:22:36]W: [Step 1/1] at java.lang.reflect.Method.invoke(Unknown Source)
[04:22:36]W: [Step 1/1] at org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:87)
[04:22:36]W: [Step 1/1] ... 9 more
[04:22:36]W: [Step 1/1] Caused by: java.lang.ClassNotFoundException: org.sonar.core.issue.IssuesBySeverity
[04:22:36]W: [Step 1/1] at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
[04:22:36]W: [Step 1/1] at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
[04:22:36]W: [Step 1/1] at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
[04:22:36]W: [Step 1/1] at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
[04:22:36]W: [Step 1/1] ... 36 more
[04:22:37]W: [Step 1/1] Process exited with code 1
[04:22:37]i: [Step 1/1] ##teamcity[buildStatisticValue key='buildStageDuration:buildStepRUNNER_325:RunSonarAnalysis_0' value='846323.0']
[04:22:37]E: [Step 1/1] Step SonarRunner (Command Line) failed

thanks in advance
Best Regards
Jorge Costa
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Jorge Costa

Build that failed is green now, I ping back if it happens again


On Sun, Apr 5, 2015, 08:48 Jorge Costa <[hidden email]> wrote:
hi guys,

i got this exception and looks to be from the new automatic assign feature
in 5.1. The analysis was ok tough, only the post job failed

[04:22:36] :             [Step 1/1] INFO:
------------------------------------------------------------------------
[04:22:36] :             [Step 1/1] INFO: EXECUTION FAILURE
[04:22:36] :             [Step 1/1] INFO:
------------------------------------------------------------------------
[04:22:36] :             [Step 1/1] Total time: 14:04.117s
[04:22:36] :             [Step 1/1] Final Memory: 55M/746M
[04:22:36]W:             [Step 1/1] ERROR: Error during Sonar runner execution
[04:22:36] :             [Step 1/1] INFO:
------------------------------------------------------------------------
[04:22:36]W:             [Step 1/1] org.sonar.runner.impl.RunnerException: Unable to
execute Sonar
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:91)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.impl.BatchLauncher$1.run(BatchLauncher.java:75)
[04:22:36]W:             [Step 1/1]     at
java.security.AccessController.doPrivileged(Native Method)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.impl.BatchLauncher.doExecute(BatchLauncher.java:69)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.impl.BatchLauncher.execute(BatchLauncher.java:50)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.api.EmbeddedRunner.doExecute(EmbeddedRunner.java:102)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.api.Runner.execute(Runner.java:90)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.Main.executeTask(Main.java:70)
[04:22:36]W:             [Step 1/1]     at org.sonar.runner.Main.execute(Main.java:59)
[04:22:36]W:             [Step 1/1]     at org.sonar.runner.Main.main(Main.java:41)
[04:22:36]W:             [Step 1/1] Caused by: java.lang.NoClassDefFoundError:
org/sonar/core/issue/IssuesBySeverity
[04:22:36]W:             [Step 1/1]     at
org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob.sendNotifications(SendIssueNotificationsPostJob.java:81)
[04:22:36]W:             [Step 1/1]     at
org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob.executeOn(SendIssueNotificationsPostJob.java:59)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.phases.PostJobsExecutor.execute(PostJobsExecutor.java:62)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.phases.PostJobsExecutor.execute(PostJobsExecutor.java:52)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.phases.DatabaseModePhaseExecutor.execute(DatabaseModePhaseExecutor.java:136)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:264)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:235)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:230)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:220)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ScanTask.scan(ScanTask.java:57)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.scan.ScanTask.execute(ScanTask.java:45)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:135)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
[04:22:36]W:             [Step 1/1]     at
org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:158)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95)
[04:22:36]W:             [Step 1/1]     at
org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.batch.IsolatedLauncher.execute(IsolatedLauncher.java:45)
[04:22:36]W:             [Step 1/1]     at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[04:22:36]W:             [Step 1/1]     at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[04:22:36]W:             [Step 1/1]     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[04:22:36]W:             [Step 1/1]     at java.lang.reflect.Method.invoke(Unknown
Source)
[04:22:36]W:             [Step 1/1]     at
org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:87)
[04:22:36]W:             [Step 1/1]     ... 9 more
[04:22:36]W:             [Step 1/1] Caused by: java.lang.ClassNotFoundException:
org.sonar.core.issue.IssuesBySeverity
[04:22:36]W:             [Step 1/1]     at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
[04:22:36]W:             [Step 1/1]     at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
[04:22:36]W:             [Step 1/1]     at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
[04:22:36]W:             [Step 1/1]     at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
[04:22:36]W:             [Step 1/1]     ... 36 more
[04:22:37]W:             [Step 1/1] Process exited with code 1
[04:22:37]i:             [Step 1/1] ##teamcity[buildStatisticValue
key='buildStageDuration:buildStepRUNNER_325:RunSonarAnalysis_0'
value='846323.0']
[04:22:37]E:             [Step 1/1] Step SonarRunner (Command Line) failed

thanks in advance



-----
Best Regards
Jorge Costa
--
View this message in context: http://sonarqube.15.x6.nabble.com/ClassNotFoundException-in-the-new-issue-assign-mechanism-in-sonar-5-1-tp5034097.html
Sent from the SonarQube Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Best Regards
Jorge Costa
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Jorge Costa
build failures are back:

java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

Seems it works in window 8 but fails in windows 7
Best Regards
Jorge Costa
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Jorge Costa
Another one:

[03:44:25][Step 1/1] 03:44:25.953 INFO  - ANALYSIS SUCCESSFUL, you can browse http://sonar:80/dashboard/index/Key
[03:44:25][Step 1/1] 03:44:25.953 INFO  - Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report.
[03:44:25][Step 1/1] 03:44:25.955 INFO  - Executing post-job class org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob
[03:44:25][Step 1/1] INFO: ------------------------------------------------------------------------
[03:44:25][Step 1/1] INFO: EXECUTION FAILURE
[03:44:25][Step 1/1] INFO: ------------------------------------------------------------------------
[03:44:25][Step 1/1] Total time: 1:50.278s
[03:44:26][Step 1/1] Final Memory: 19M/401M
[03:44:26][Step 1/1] INFO: ------------------------------------------------------------------------
[03:44:26][Step 1/1] ERROR: Error during Sonar runner execution
[03:44:26][Step 1/1] ERROR: Unable to execute Sonar
[03:44:26][Step 1/1] ERROR: Caused by: org/sonar/core/issue/IssuesBySeverity
[03:44:26][Step 1/1] ERROR: Caused by: org.sonar.core.issue.IssuesBySeverity
[03:44:26][Step 1/1] ERROR:
[03:44:26][Step 1/1] ERROR: To see the full stack trace of the errors, re-run SonarQube Runner with the -e switch.
[03:44:26][Step 1/1] ERROR: Re-run SonarQube Runner using the -X switch to enable full debug logging.
[03:44:26][Step 1/1] Process exited with code 1
[03:44:26][Step 1/1] Step SonarRunner (Command Line) failed

How can i disable the this assign feature in Core?
Best Regards
Jorge Costa
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Julien Lancelot
Hi Jorge,

Your issue is coming from the "Issue Assign Plugin", which seems to be no more compatible with SonarQube 5.1, because it's using an internal class (org.sonar.core.issue.IssuesBySeverity) that doesn't exists anymore.
Remove this plugin and everything should work !

And you'll be able to use the new issue auto assign feature from the platform.

+++

Julien LANCELOT | SonarSource

On 9 April 2015 at 08:11, Jorge Costa <[hidden email]> wrote:
Another one:

[03:44:25][Step 1/1] 03:44:25.953 INFO  - ANALYSIS SUCCESSFUL, you can
browse http://sonar:80/dashboard/index/Key
[03:44:25][Step 1/1] 03:44:25.953 INFO  - Note that you will be able to
access the updated dashboard once the server has processed the submitted
analysis report.
[03:44:25][Step 1/1] 03:44:25.955 INFO  - Executing post-job class
org.sonar.plugins.issueassign.notification.SendIssueNotificationsPostJob
[03:44:25][Step 1/1] INFO:
------------------------------------------------------------------------
[03:44:25][Step 1/1] INFO: EXECUTION FAILURE
[03:44:25][Step 1/1] INFO:
------------------------------------------------------------------------
[03:44:25][Step 1/1] Total time: 1:50.278s
[03:44:26][Step 1/1] Final Memory: 19M/401M
[03:44:26][Step 1/1] INFO:
------------------------------------------------------------------------
[03:44:26][Step 1/1] ERROR: Error during Sonar runner execution
[03:44:26][Step 1/1] ERROR: Unable to execute Sonar
[03:44:26][Step 1/1] ERROR: Caused by: org/sonar/core/issue/IssuesBySeverity
[03:44:26][Step 1/1] ERROR: Caused by: org.sonar.core.issue.IssuesBySeverity
[03:44:26][Step 1/1] ERROR:
[03:44:26][Step 1/1] ERROR: To see the full stack trace of the errors,
re-run SonarQube Runner with the -e switch.
[03:44:26][Step 1/1] ERROR: Re-run SonarQube Runner using the -X switch to
enable full debug logging.
[03:44:26][Step 1/1] Process exited with code 1
[03:44:26][Step 1/1] Step SonarRunner (Command Line) failed

How can i disable the this assign feature in Core?



-----
Best Regards
Jorge Costa
--
View this message in context: http://sonarqube.15.x6.nabble.com/ClassNotFoundException-in-the-new-issue-assign-mechanism-in-sonar-5-1-tp5034097p5034168.html
Sent from the SonarQube Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Jorge Costa
ok great... thanks Julien
Best Regards
Jorge Costa
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

gryphius
This post has NOT been accepted by the mailing list yet.
In reply to this post by Julien Lancelot
But is this everything to say about it, removing the plugin?

If you go to update center this issue assign plugin is offered for SonarQube 5.1.

If it is not meant to be used for 5.1 version I suggest that it is not offered anymore in the update center for this version, applying poka-yoke principle. And it should not be installed even if someone copies it into the plugins folder.
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Ernesto Maserati
In reply to this post by Jorge Costa
But is this everything to say about it, removing the plugin to avoid NoClassDefFoundError, Julien?

If you go to update center this issue assign plugin is offered for SonarQube 5.1.

If it is not meant to be used for 5.1 version I suggest that it is not offered anymore in the update center for this version, applying poka-yoke principle. And it should not be installed even if someone copies it into the plugins folder.
Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Julien Lancelot
Hi Ernesto,

I've checked just now, and in SonarQube 5.1 the Issue Assign Plugin is not available in the list of availables plugin of the update center. Please check again and tell me if you still see it.

If someone is copying manually a incompatible plugin in the plugins folder (which is NOT the advised way to install a plugin), we have no way for the moment to detect it and fail (no internet connexion is required when starting the server).

Regards,

Julien LANCELOT | SonarSource

On 15 April 2015 at 13:09, Ernesto Maserati <[hidden email]> wrote:
But is this everything to say about it, removing the plugin to avoid NoClassDefFoundError, Julien?

If you go to update center this issue assign plugin is offered for SonarQube 5.1.

If it is not meant to be used for 5.1 version I suggest that it is not offered anymore in the update center for this version, applying poka-yoke principle. And it should not be installed even if someone copies it into the plugins folder.

Reply | Threaded
Open this post in threaded view
|

Re: ClassNotFoundException in the new issue assign mechanism in sonar 5.1

Ernesto Maserati
It is not displayed anymore as "Available Updates", thank you.

This was the most important thing to prevent that problem for users I think.

The other thing would be some plugin version range mechanism like OSGi has to avoid installing extension which is not meant for another application version. But that would be just an improvement of course.

On Thu, Apr 16, 2015 at 10:31 AM, Julien Lancelot <[hidden email]> wrote:
Hi Ernesto,

I've checked just now, and in SonarQube 5.1 the Issue Assign Plugin is not available in the list of availables plugin of the update center. Please check again and tell me if you still see it.

If someone is copying manually a incompatible plugin in the plugins folder (which is NOT the advised way to install a plugin), we have no way for the moment to detect it and fail (no internet connexion is required when starting the server).

Regards,

Julien LANCELOT | SonarSource

On 15 April 2015 at 13:09, Ernesto Maserati <[hidden email]> wrote:
But is this everything to say about it, removing the plugin to avoid NoClassDefFoundError, Julien?

If you go to update center this issue assign plugin is offered for SonarQube 5.1.

If it is not meant to be used for 5.1 version I suggest that it is not offered anymore in the update center for this version, applying poka-yoke principle. And it should not be installed even if someone copies it into the plugins folder.