Exception : javax.persistence.NonUniqueResultException: result returns more than one elements

On other projects we get this exception:

org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Can not execute Sonar
at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:87)
at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:65)
at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:117)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: java.lang.IllegalArgumentException: Measure.metric can not be null. Please check that the metric is defined in Plugin.getExtensions().
at org.sonar.batch.DefaultSensorContext.createMeasure(DefaultSensorContext.java:372)
at org.sonar.batch.DefaultSensorContext.persistMeasure(DefaultSensorContext.java:354)
at org.sonar.batch.DefaultSensorContext.saveMeasure(DefaultSensorContext.java:115)
at org.sonar.batch.DefaultSensorContext.saveMeasure(DefaultSensorContext.java:105)
at org.sonar.batch.DefaultDecoratorContext.saveMeasure(DefaultDecoratorContext.java:120)
at org.sonar.plugins.technicaldebt.TechnicalDebtDecorator.saveMeasure(TechnicalDebtDecorator.java:120)
at org.sonar.plugins.technicaldebt.TechnicalDebtDecorator.decorate(TechnicalDebtDecorator.java:113)
at org.sonar.batch.core.DecoratorsExecutor.decorateResource(DecoratorsExecutor.java:86)
at org.sonar.batch.core.DecoratorsExecutor.decorateResource(DecoratorsExecutor.java:71)
at org.sonar.batch.core.DecoratorsExecutor.decorateResource(DecoratorsExecutor.java:71)
at org.sonar.batch.core.DecoratorsExecutor.execute(DecoratorsExecutor.java:62)
at org.sonar.batch.Batch.executeJobs(Batch.java:91)
at org.sonar.batch.Batch.analyse(Batch.java:79)
at org.sonar.batch.Batch.start(Batch.java:54)
at org.sonar.batch.Batch.start(Batch.java:50)
at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:82)
... 20 more

Hi Markus,
From which version did you upgrade ?

We did upgrade from 1.10.

Markus, to make it simpler, I have created SONAR-1200 for your second issue.

Are you analyzing a project and separately one of its module ?

Markus, this error occurs when the same file exists in the test and src directories.

Hi Freddy,
We have sonar running only on the top-level maven projects from our hudson server. So we are not analyzing a project and one of its modules as well.
And also it should not be the case that there is the same file in the src and test directory (but I'm not sure about this).
At least it would be good to give the user some more information (e.g. which file is duplicated).

Hi Markus, could you try to launch a new "mvn sonar:sonar" command but with the "-e" Maven options as we should get some contextual information (SONAR-597).
Thanks

Doesn't the sonar-hudson plugin call sonar with -e?

Here is the full hudson sonar output:

+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'sonar'.
[INFO] ------------------------------------------------------------------------
[INFO] Building IS-Control
[INFO] task-segment: [sonar:sonar] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [sonar:sonar {execution: default-cli}]
[INFO] Sonar host: http://buildserver02.office.nmmn.com:8180/sonar
[INFO] Sonar version: 1.11
[INFO] [sonar-core:internal {execution: default-internal}]
[INFO] ------------- Analyse IS-Control...
[INFO] Selected quality profile : llynch, language=java
[INFO] Configure maven plugins...
[INFO] Executing sensor class org.sonar.plugins.core.sensors.JavaSourceImporter
[WARN] NonUniqueResultException on entity ResourceModel with criterias : key,de.nmmn.iscontrol:iscontrol-frontend:de.nmmn.iscontrol.InitializationListener
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can not execute Sonar

Embedded error: result returns more than one elements
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Can not execute Sonar
at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:87)
at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:65)
at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:117)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: javax.persistence.NonUniqueResultException: result returns more than one elements
at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:109)
at org.sonar.api.database.DatabaseSession.getSingleResult(DatabaseSession.java:161)
at org.sonar.api.database.DatabaseSession.getSingleResult(DatabaseSession.java:174)
at org.sonar.batch.DefaultSensorContext.createResource(DefaultSensorContext.java:317)
at org.sonar.batch.DefaultSensorContext.saveSnapshot(DefaultSensorContext.java:304)
at org.sonar.batch.DefaultSensorContext.saveSource(DefaultSensorContext.java:194)
at org.sonar.api.batch.AbstractSourceImporter.parseDirs(AbstractSourceImporter.java:80)
at org.sonar.api.batch.AbstractSourceImporter.analyse(AbstractSourceImporter.java:71)
at org.sonar.api.batch.AbstractSourceImporter.analyse(AbstractSourceImporter.java:63)
at org.sonar.batch.core.SensorsExecutor.execute(SensorsExecutor.java:59)
at org.sonar.batch.Batch.executeJobs(Batch.java:91)
at org.sonar.batch.Batch.analyse(Batch.java:79)
at org.sonar.batch.Batch.start(Batch.java:54)
at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:82)
... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15 seconds
[INFO] Finished at: Fri Oct 09 12:36:34 CEST 2009
[INFO] Final Memory: 10M/23M
[INFO] ------------------------------------------------------------------------

You're right markus, I've created SONARPLUGINS-253 to automatically add the "-e" parameter.
In your case, the file de/nmmn/iscontrol/InitializationListener.java seems to be both in your tests and src directories of your IS-Control (de.nmmn.iscontrol/iscontrol-frontend) Maven module.

I've double checked that and the file is not in src and test path and also I wiped the whole hudson workspace and that does not help.
Any other idea?

Could you execute the following SQL request Markus and add a comment to this ticket with the result :

select * from projects where kee = 'de.nmmn.iscontrol:iscontrol-frontend:de.nmmn.iscontrol.InitializationListener'

This is the result. Could this have happened because we had the project/module twice in the database before?
But we deleted it and it should be there only once?

+------+------------------------+-------------+---------+-------+-----------+-------------------------------------------------------------------------------+---------+------------+----------+------------------+
| id   | name                   | description | enabled | scope | qualifier | kee                                                                           | root_id | profile_id | language | copy_resource_id |
+------+------------------------+-------------+---------+-------+-----------+-------------------------------------------------------------------------------+---------+------------+----------+------------------+
| 1784 | InitializationListener | NULL        |       1 | FIL   | CLA       | de.nmmn.iscontrol:iscontrol-frontend:de.nmmn.iscontrol.InitializationListener |    1767 |       NULL | java     |             NULL | 
| 5062 | InitializationListener | NULL        |       1 | FIL   | CLA       | de.nmmn.iscontrol:iscontrol-frontend:de.nmmn.iscontrol.InitializationListener |    5058 |       NULL | java     |             NULL | 
+------+------------------------+-------------+---------+-------+-----------+-------------------------------------------------------------------------------+---------+------------+----------+------------------+

Could you now execute the following SQL request :

select * from projects where id in (1767, 5058)

thanks

The result of the statement is:

+------+------------+-------------+---------+-------+-----------+--------------------------------------+---------+------------+----------+------------------+
| id   | name       | description | enabled | scope | qualifier | kee                                  | root_id | profile_id | language | copy_resource_id |
+------+------------+-------------+---------+-------+-----------+--------------------------------------+---------+------------+----------+------------------+
| 5058 | IS-Control | NULL        |       1 | PRJ   | TRK       | de.nmmn.iscontrol:iscontrol-frontend |    NULL |       NULL | java     |             NULL | 
+------+------------+-------------+---------+-------+-----------+--------------------------------------+---------+------------+----------+------------------+

Ok Markus, executing the following SQL Request should fix your issue :

delete from projects where id=1784

But I don't know yet how to reproduce this issue.

That helped. But I saw that we have nearly 80 other duplicates in our database.
I'll delete this now and hope that it does work afterwards.

Thanks for any help Freddy.
And keep on - I love sonar - its a great tool.

This happened to us on about 10 of our 60 hudson jobs...here is one example. Is there some generic thing we can do to cleanup the database? Was it caused by a migration to Sonar 1.11.1 (from 1.9.2) in the database?

[INFO] task-segment: [sonar:sonar] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [sonar:sonar {execution: default-cli}]
[INFO] Sonar host: http://metrics.nanometrics.ca
[INFO] Sonar version: 1.11.1
[INFO] [sonar-core:internal {execution: default-internal}]
[INFO] ------------- Analyse Apollo Core...
[INFO] Selected quality profile : Nanometrics, language=java
[INFO] Configure maven plugins...
[INFO] Executing sensor class org.sonar.plugins.core.sensors.JavaSourceImporter
[WARN] NonUniqueResultException on entity ResourceModel with criterias : key,ca.nanometrics.apollo:apollo-core:ca.nanometrics.apollo.core.seismic.traveltime
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can not execute Sonar

Embedded error: result returns more than one elements
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Can not execute Sonar
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Can not execute Sonar
at org.sonar.mojo.bootstrap.Bootstraper.executeMojo(Bootstraper.java:79)
at org.sonar.mojo.bootstrap.Bootstraper.start(Bootstraper.java:62)
at org.sonar.mojo.bootstrap.SonarMojo.execute(SonarMojo.java:112)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: javax.persistence.NonUniqueResultException: result returns more than one elements
at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:109)
at org.sonar.api.database.DatabaseSession.getSingleResult(DatabaseSession.java:161)
at org.sonar.api.database.DatabaseSession.getSingleResult(DatabaseSession.java:174)
at org.sonar.batch.DefaultSensorContext.createResource(DefaultSensorContext.java:317)
at org.sonar.batch.DefaultSensorContext.saveSnapshot(DefaultSensorContext.java:304)
at org.sonar.batch.DefaultSensorContext.saveSnapshot(DefaultSensorContext.java:301)
at org.sonar.batch.DefaultSensorContext.saveSource(DefaultSensorContext.java:194)
at org.sonar.api.batch.AbstractSourceImporter.parseDirs(AbstractSourceImporter.java:80)
at org.sonar.api.batch.AbstractSourceImporter.analyse(AbstractSourceImporter.java:71)
at org.sonar.api.batch.AbstractSourceImporter.analyse(AbstractSourceImporter.java:63)
at org.sonar.batch.core.SensorsExecutor.execute(SensorsExecutor.java:59)
at org.sonar.batch.Batch.executeJobs(Batch.java:91)
at org.sonar.batch.Batch.analyse(Batch.java:79)
at org.sonar.batch.Batch.start(Batch.java:54)
at org.sonar.batch.BatchMojo.executeBatch(BatchMojo.java:138)
at org.sonar.batch.BatchMojo.execute(BatchMojo.java:130)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.sonar.mojo.bootstrap.Bootstraper.executeMojo(Bootstraper.java:76)
... 21 more

It seems to me that this bug (at least in my case) comes down to a case-insensitive check meaning that you can't have class and package name being the same:

-----------------------------------------------------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------------------------------------------------

In this case, I have a ca.nanometrics.util.Progress.class in the parent package of package ca.nanometrics.util.progress.

This then leads to the same exception...

Ben, looks like your issue is the SONAR-1243. Can you have a look in the comment, there is a work around.