atom feed9 messages in org.codehaus.sonar.user[sonar-user] IllegalStateException: C...
FromSent OnAttachments
pete...@css.chFeb 8, 2012 12:35 am 
Evgeny MandrikovFeb 8, 2012 1:08 am 
pete...@css.chFeb 8, 2012 5:56 am 
Evgeny MandrikovFeb 8, 2012 11:13 pm 
pete...@css.chFeb 9, 2012 1:30 am 
Evgeny MandrikovFeb 9, 2012 2:36 am 
pete...@css.chFeb 9, 2012 10:23 am 
pete...@css.chFeb 10, 2012 3:08 am 
Evgeny MandrikovFeb 10, 2012 2:37 pm 
Subject:[sonar-user] IllegalStateException: Can not create ClassLoader
From:pete...@css.ch (pete@css.ch)
Date:Feb 8, 2012 12:35:17 am
List:org.codehaus.sonar.user

Hi all

I have 3 projects (among some 50+ others) which cannot be analysed with sonar. I use ant for analysis (latest ant task with version 1.3; Sonar server is the latest release 2.13.1 deployed on Tomcat 6 / Java 1.6).

I get the following error output:

[..] [sonar:sonar] 03:23:32.037 INFO Java AST scan... [sonar:sonar] 03:23:34.178 INFO Java AST scan done: 2141 ms [sonar:sonar] 03:23:34.179 INFO Java bytecode scan... [sonar:sonar] java.lang.IllegalStateException: Can not create ClassLoader Sonar excection failure. Reason: java.lang.IllegalStateException: Can not create ClassLoader

The problematic projects could be analysed with older versions of sonar (version <= 2.10). Unfortunately, not only the sonar version changed since then but also the plugin set and the ant task version. It would therefore be helpful to know where to look for the cause of this problem.

The following plugins (other than the core plugins coming with sonar) are installed.

- ch.css.sonar.filter.resource-0.0.6.jar - ch.css.sonar.metrics.build-0.6.1.jar - sonar-artifact-size-plugin-0.3.jar - sonar-branding-plugin-0.3.jar - sonar-clirr-plugin-1.1.jar - sonar-clover-plugin-2.8.jar - sonar-csv-export-plugin-1.2.jar - sonar-cutoff-plugin-0.1.1.jar - sonar-emma-plugin-1.2.1.jar - sonar-fb-contrib-plugin-1.1.jar - sonar-jira-plugin-0.3.jar - sonar-ldap-plugin-1.0.jar - sonar-quality-index-plugin-1.1.3.jar - sonar-radiator-plugin-1.1.jar - sonar-scm-activity-plugin-1.3.jar - sonar-security-rules-plugin-0.3.2.jar - sonar-sigmm-plugin-1.0.1.jar - sonar-sonargraph-plugin-3.0.2.jar - sonar-switch-off-violations-plugin-1.0.jar - sonar-taglist-plugin-1.1.7.jar - sonar-technicaldebt-plugin-1.2.1.jar - sonar-total-quality-plugin-1.0.2.jar - sonar-useless-code-tracker-plugin-0.4.jar - sonar-violationdensity-plugin-1.2.jar

Is this a known problem (googling for it didn't lead to any hints)? Is it possible to say if this is caused by a plugin or by sonar (and its core plugins) itself? Which is the most efficient way to get to the root cause: Increasing log levels or successive de-installation of plugins till the error vanishes (which is time consuming)? Other ideas?

Any help would be welcome.

Peter Waldispühl