Sonar 2.11 Embedded error: PicoLifecycleException:

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

Sonar 2.11 Embedded error: PicoLifecycleException:

bedouin-2
Hello,

We have upgrade sonar from 1.12 to 2.11.

We have completely started from scratch, i.e. deleted all data, tables, indexes etc from the former Oracle DB.

So basically we have started completely with a clean fresh Sonar 2.11

We run Sonar from Hudson and we have the following problem.
We have made some research and the problem is supposed to have been fixed in Sonar 2.8...

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can not execute Sonar

Embedded error: PicoLifecycleException: method 'public void org.sonar.batch.ProjectTree.start() throws java.io.IOException', instance 'org.sonar.batch.ProjectTree@1fffa73, javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
[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: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:103)
    at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:79)
    at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:88)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
    ... 17 more
Caused by: org.picocontainer.PicoLifecycleException: PicoLifecycleException: method 'public void org.sonar.batch.ProjectTree.start() throws java.io.IOException', instance 'org.sonar.batch.ProjectTree@1fffa73, javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
    at org.picocontainer.monitors.NullComponentMonitor.lifecycleInvocationFailed(NullComponentMonitor.java:77)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.monitorAndThrowReflectionLifecycleException(ReflectionLifecycleStrategy.java:132)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:115)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.start(ReflectionLifecycleStrategy.java:89)
    at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.start(AbstractInjectionFactory.java:84)
    at org.picocontainer.behaviors.AbstractBehavior.start(AbstractBehavior.java:169)
    at org.picocontainer.behaviors.Stored$RealComponentLifecycle.start(Stored.java:132)
    at org.picocontainer.behaviors.Stored.start(Stored.java:110)
    at org.picocontainer.DefaultPicoContainer.potentiallyStartAdapter(DefaultPicoContainer.java:996)
    at org.picocontainer.DefaultPicoContainer.startAdapters(DefaultPicoContainer.java:989)
    at org.picocontainer.DefaultPicoContainer.start(DefaultPicoContainer.java:746)
    at org.sonar.batch.bootstrap.Module.start(Module.java:88)
    at org.sonar.batch.bootstrap.BootstrapModule.doStart(BootstrapModule.java:96)
    at org.sonar.batch.bootstrap.Module.start(Module.java:89)
    at org.sonar.batch.Batch.execute(Batch.java:74)
    at org.sonar.maven.SonarMojo.executeBatch(SonarMojo.java:154)
    at org.sonar.maven.SonarMojo.execute(SonarMojo.java:143)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:98)
    ... 21 more
Caused by: javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
    at org.sonar.jpa.session.JpaDatabaseSession.getSingleResult(JpaDatabaseSession.java:194)
    at org.sonar.jpa.session.JpaDatabaseSession.getSingleResult(JpaDatabaseSession.java:212)
    at org.sonar.batch.ProjectConfigurator.isLatestAnalysis(ProjectConfigurator.java:106)
    at org.sonar.batch.ProjectConfigurator.configure(ProjectConfigurator.java:83)
    at org.sonar.batch.ProjectConfigurator.configure(ProjectConfigurator.java:78)
    at org.sonar.batch.ProjectTree.doStart(ProjectTree.java:83)
    at org.sonar.batch.ProjectTree.start(ProjectTree.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:585)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:110)
    ... 37 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 2 seconds
[INFO] Finished at: Thu Nov 03 10:53:03 CET 2011
[INFO] Final Memory: 30M/202M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: xxxxxxxxxxxxxxxxxxxxxxxxxxx
[DEBUG] Skipping watched dependency update for build: exempleAvecProfile_as-jonas #227 due to result: FAILURE
Finished: FAILURE

thks.
--
Nourredine Rouibah
[hidden email]
Wherever I go, there I am...

Reply | Threaded
Open this post in threaded view
|

Re: Sonar 2.11 Embedded error: PicoLifecycleException:

Freddy Mallet SonarSource
Hi Nourredine,

The only known limitation which can lead to such issue is that Sonar doesn't support parallel runs on the SAME project :


Could you execute the following SQL request and send back the result ?

select * from snapshots where project_id=10533

Thanks
Freddy

Freddy MALLET | SonarSource
http://sonarsource.com



On Thu, Nov 3, 2011 at 11:13 AM, Nourredine Rouibah <[hidden email]> wrote:
Hello,

We have upgrade sonar from 1.12 to 2.11.

We have completely started from scratch, i.e. deleted all data, tables, indexes etc from the former Oracle DB.

So basically we have started completely with a clean fresh Sonar 2.11

We run Sonar from Hudson and we have the following problem.
We have made some research and the problem is supposed to have been fixed in Sonar 2.8...

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Can not execute Sonar

Embedded error: PicoLifecycleException: method 'public void org.sonar.batch.ProjectTree.start() throws java.io.IOException', instance 'org.sonar.batch.ProjectTree@1fffa73, javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
[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: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:103)
    at org.codehaus.mojo.sonar.Bootstraper.start(Bootstraper.java:79)
    at org.codehaus.mojo.sonar.SonarMojo.execute(SonarMojo.java:88)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
    ... 17 more
Caused by: org.picocontainer.PicoLifecycleException: PicoLifecycleException: method 'public void org.sonar.batch.ProjectTree.start() throws java.io.IOException', instance 'org.sonar.batch.ProjectTree@1fffa73, javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
    at org.picocontainer.monitors.NullComponentMonitor.lifecycleInvocationFailed(NullComponentMonitor.java:77)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.monitorAndThrowReflectionLifecycleException(ReflectionLifecycleStrategy.java:132)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:115)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.start(ReflectionLifecycleStrategy.java:89)
    at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.start(AbstractInjectionFactory.java:84)
    at org.picocontainer.behaviors.AbstractBehavior.start(AbstractBehavior.java:169)
    at org.picocontainer.behaviors.Stored$RealComponentLifecycle.start(Stored.java:132)
    at org.picocontainer.behaviors.Stored.start(Stored.java:110)
    at org.picocontainer.DefaultPicoContainer.potentiallyStartAdapter(DefaultPicoContainer.java:996)
    at org.picocontainer.DefaultPicoContainer.startAdapters(DefaultPicoContainer.java:989)
    at org.picocontainer.DefaultPicoContainer.start(DefaultPicoContainer.java:746)
    at org.sonar.batch.bootstrap.Module.start(Module.java:88)
    at org.sonar.batch.bootstrap.BootstrapModule.doStart(BootstrapModule.java:96)
    at org.sonar.batch.bootstrap.Module.start(Module.java:89)
    at org.sonar.batch.Batch.execute(Batch.java:74)
    at org.sonar.maven.SonarMojo.executeBatch(SonarMojo.java:154)
    at org.sonar.maven.SonarMojo.execute(SonarMojo.java:143)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.codehaus.mojo.sonar.Bootstraper.executeMojo(Bootstraper.java:98)
    ... 21 more
Caused by: javax.persistence.NonUniqueResultException: Expected single result, but got : [Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]]
    at org.sonar.jpa.session.JpaDatabaseSession.getSingleResult(JpaDatabaseSession.java:194)
    at org.sonar.jpa.session.JpaDatabaseSession.getSingleResult(JpaDatabaseSession.java:212)
    at org.sonar.batch.ProjectConfigurator.isLatestAnalysis(ProjectConfigurator.java:106)
    at org.sonar.batch.ProjectConfigurator.configure(ProjectConfigurator.java:83)
    at org.sonar.batch.ProjectConfigurator.configure(ProjectConfigurator.java:78)
    at org.sonar.batch.ProjectTree.doStart(ProjectTree.java:83)
    at org.sonar.batch.ProjectTree.start(ProjectTree.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:585)
    at org.picocontainer.lifecycle.ReflectionLifecycleStrategy.invokeMethod(ReflectionLifecycleStrategy.java:110)
    ... 37 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 2 seconds
[INFO] Finished at: Thu Nov 03 10:53:03 CET 2011
[INFO] Final Memory: 30M/202M
[INFO] ------------------------------------------------------------------------
Sending e-mails to: xxxxxxxxxxxxxxxxxxxxxxxxxxx
[DEBUG] Skipping watched dependency update for build: exempleAvecProfile_as-jonas #227 due to result: FAILURE
Finished: FAILURE

thks.
--
Nourredine Rouibah
[hidden email]
Wherever I go, there I am...


Reply | Threaded
Open this post in threaded view
|

Re: Sonar 2.11 Embedded error: PicoLifecycleException:

Torbjörn Hultén
I've been following this issue for quite some time and I do not think this is the only circumstance under which it appears. We first installed Sonar 2.7 and soon after upgraded to 2.7.1. I read that the issue should have been solved in 2.8, but by the time we got around to update 2.10 had been released and that is the version we are running at the moment.

Today I "fixed" our database (again) by running the one-liner suggested in one of the related Jira issues.

update snapshots old_snap, snapshots new_snap set old_snap.islast=0 where old_snap.islast=1 and new_snap.created_at > old_snap.created_at and new_snap.project_id = old_snap.project_id and new_snap.islast=1

This resulted in 58 rows being updated.

The project in which the issue was noticed is a relatively new one (created post 2.10) and is relatively simple (i.e. no sub modules). The sonar analysis is only performed by our Jenkins build server and the likelihood of anybody running it manually is very slim, let alone simultaneously.

Is there anything I could do to help in trying to isolate the cause? It is intermittent and I haven't been able to find a pattern so far. I'm not able to disclose any actual data, but perhaps I could do some interesting database queries the next time it appears?

Sonar 2.10 on mysql, maven 3.0.3 with org.codehaus.mojo:sonar-maven-plugin:2.0 (with lots of 2.10 dependencies), centos 5.5.

Regards
Torbjörn

Freddy Mallet-3 wrote
The only known limitation which can lead to such issue is that Sonar
doesn't support parallel runs on the SAME project :

http://jira.codehaus.org/browse/SONAR-2761
Reply | Threaded
Open this post in threaded view
|

Re: Sonar 2.11 Embedded error: PicoLifecycleException:

Freddy Mallet
Hi Torbjöm,

I'm sorry to come back to my first suggestion but according to your error message I'm really pretty sure that two Sonar analysis have been launched almost simultaneously on the same project as there is only 263 ms between the two snapshots on the project :

Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.094,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598], 

Snapshot[resourceId=10533,createdAt=2011-11-01 21:03:28.259,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]

-----
Sonar for Continuous Inspection



On Wed, Dec 7, 2011 at 5:46 PM, Torbjörn Hultén <[hidden email]> wrote:

I've been following this issue for quite some time and I do not think this is
the only circumstance under which it appears. We first installed Sonar 2.7
and soon after upgraded to 2.7.1. I read that the issue should have been
solved in 2.8, but by the time we got around to update 2.10 had been
released and that is the version we are running at the moment.

Today I "fixed" our database (again) by running the one-liner suggested in
one of the related Jira issues.

update snapshots old_snap, snapshots new_snap set old_snap.islast=0 where
old_snap.islast=1 and new_snap.created_at > old_snap.created_at and
new_snap.project_id = old_snap.project_id and new_snap.islast=1

This resulted in 58 rows being updated.

The project in which the issue was noticed is a relatively new one (created
post 2.10) and is relatively simple (i.e. no sub modules). The sonar
analysis is only performed by our Jenkins build server and the likelihood of
anybody running it manually is very slim, let alone simultaneously.

Is there anything I could do to help in trying to isolate the cause? It is
intermittent and I haven't been able to find a pattern so far. I'm not able
to disclose any actual data, but perhaps I could do some interesting
database queries the next time it appears?

Sonar 2.10 on mysql, maven 3.0.3 with
org.codehaus.mojo:sonar-maven-plugin:2.0 (with lots of 2.10 dependencies),
centos 5.5.

Regards
Torbjörn


Freddy Mallet-3 wrote:
>
> The only known limitation which can lead to such issue is that Sonar
> doesn't support parallel runs on the SAME project :
>
> http://jira.codehaus.org/browse/SONAR-2761
>

--
View this message in context: http://old.nabble.com/Sonar-2.11-Embedded-error%3A-PicoLifecycleException%3A-tp32771678p32929912.html
Sent from the Sonar user 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: Sonar 2.11 Embedded error: PicoLifecycleException:

Daniel Jeliński
Hello Freddy,
I am facing the same problem and I am certain that no analyses have been  
launched simultaneously. All analyses are done by a single Jenkins server  
which is set to a single worker thread.

Also, the problem is repetitive, that is after running the suggested  
update I get a single successful analysis, after which the problem returns.

Also, the second of the snapshots points to the first, that is,  
parent_snapshot_id of the second row equals to id of the first row.

Any ideas?

Regards,
Daniel


Dnia 09-12-2011 o 14:09:08 Freddy Mallet <[hidden email]>  
napisał(a):

> Hi Torbjöm,
>
> I'm sorry to come back to my first suggestion but according to your error
> message I'm really pretty sure that two Sonar analysis have been launched
> almost simultaneously on the same project as there is only 263 ms between
> the two snapshots on the project :
>
> Snapshot[resourceId=10533,createdAt=*2011-11-01
> 21:03:28.094*,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31
> 21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02
> 21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598],
>
> Snapshot[resourceId=10533,createdAt=*2011-11-01
> 21:03:28.259*,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31
> 21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02
> 21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]
>
> -----
> twitter.com/FreddyMallet
> Sonar for Continuous Inspection
>
>
>
> On Wed, Dec 7, 2011 at 5:46 PM, Torbjörn Hultén
> <[hidden email]>wrote:
>
>>
>> I've been following this issue for quite some time and I do not think  
>> this
>> is
>> the only circumstance under which it appears. We first installed Sonar  
>> 2.7
>> and soon after upgraded to 2.7.1. I read that the issue should have been
>> solved in 2.8, but by the time we got around to update 2.10 had been
>> released and that is the version we are running at the moment.
>>
>> Today I "fixed" our database (again) by running the one-liner suggested  
>> in
>> one of the related Jira issues.
>>
>> update snapshots old_snap, snapshots new_snap set old_snap.islast=0  
>> where
>> old_snap.islast=1 and new_snap.created_at > old_snap.created_at and
>> new_snap.project_id = old_snap.project_id and new_snap.islast=1
>>
>> This resulted in 58 rows being updated.
>>
>> The project in which the issue was noticed is a relatively new one  
>> (created
>> post 2.10) and is relatively simple (i.e. no sub modules). The sonar
>> analysis is only performed by our Jenkins build server and the  
>> likelihood
>> of
>> anybody running it manually is very slim, let alone simultaneously.
>>
>> Is there anything I could do to help in trying to isolate the cause? It  
>> is
>> intermittent and I haven't been able to find a pattern so far. I'm not  
>> able
>> to disclose any actual data, but perhaps I could do some interesting
>> database queries the next time it appears?
>>
>> Sonar 2.10 on mysql, maven 3.0.3 with
>> org.codehaus.mojo:sonar-maven-plugin:2.0 (with lots of 2.10  
>> dependencies),
>> centos 5.5.
>>
>> Regards
>> Torbjörn
>>
>>
>> Freddy Mallet-3 wrote:
>> >
>> > The only known limitation which can lead to such issue is that Sonar
>> > doesn't support parallel runs on the SAME project :
>> >
>> > http://jira.codehaus.org/browse/SONAR-2761
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Sonar-2.11-Embedded-error%3A-PicoLifecycleException%3A-tp32771678p32929912.html
>> Sent from the Sonar user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>>


--
Używam klienta poczty Opera Mail: http://www.opera.com/mail/

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

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Sonar 2.11 Embedded error: PicoLifecycleException:

Freddy Mallet
Hi Daniel, are you also using Oracle and Sonar 2.11 ?
-----
Sonar for Continuous Inspection



2011/12/9 Daniel Jeliński <[hidden email]>
Hello Freddy,
I am facing the same problem and I am certain that no analyses have been launched simultaneously. All analyses are done by a single Jenkins server which is set to a single worker thread.

Also, the problem is repetitive, that is after running the suggested update I get a single successful analysis, after which the problem returns.

Also, the second of the snapshots points to the first, that is, parent_snapshot_id of the second row equals to id of the first row.

Any ideas?

Regards,
Daniel


Dnia 09-12-2011 o 14:09:08 Freddy Mallet <[hidden email]> napisał(a):

Hi Torbjöm,

I'm sorry to come back to my first suggestion but according to your error
message I'm really pretty sure that two Sonar analysis have been launched
almost simultaneously on the same project as there is only 263 ms between
the two snapshots on the project :

Snapshot[resourceId=10533,createdAt=*2011-11-01
21:03:28.094*,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31

21:03:23.338,period2Date=2011-10-27 21:03:28.094,period3Date=2011-10-02
21:03:28.094,period4Date=<null>,period5Date=<null>,id=28598],

Snapshot[resourceId=10533,createdAt=*2011-11-01
21:03:28.259*,version=3.2.3-SNAPSHOT,last=true,status=P,scope=PRJ,path=<null>,depth=0,qualifier=TRK,rootId=<null>,parentId=<null>,rootProjectId=10533,period1Mode=previous_analysis,period2Mode=days,period3Mode=days,period4Mode=<null>,period5Mode=<null>,period1Param=2011-10-31,period2Param=5,period3Param=30,period4Param=<null>,period5Param=<null>,period1Date=2011-10-31

21:03:23.338,period2Date=2011-10-27 21:03:28.259,period3Date=2011-10-02
21:03:28.259,period4Date=<null>,period5Date=<null>,id=28599]

-----
twitter.com/FreddyMallet
Sonar for Continuous Inspection



On Wed, Dec 7, 2011 at 5:46 PM, Torbjörn Hultén
<[hidden email]>wrote:


I've been following this issue for quite some time and I do not think this
is
the only circumstance under which it appears. We first installed Sonar 2.7
and soon after upgraded to 2.7.1. I read that the issue should have been
solved in 2.8, but by the time we got around to update 2.10 had been
released and that is the version we are running at the moment.

Today I "fixed" our database (again) by running the one-liner suggested in
one of the related Jira issues.

update snapshots old_snap, snapshots new_snap set old_snap.islast=0 where
old_snap.islast=1 and new_snap.created_at > old_snap.created_at and
new_snap.project_id = old_snap.project_id and new_snap.islast=1

This resulted in 58 rows being updated.

The project in which the issue was noticed is a relatively new one (created
post 2.10) and is relatively simple (i.e. no sub modules). The sonar
analysis is only performed by our Jenkins build server and the likelihood
of
anybody running it manually is very slim, let alone simultaneously.

Is there anything I could do to help in trying to isolate the cause? It is
intermittent and I haven't been able to find a pattern so far. I'm not able
to disclose any actual data, but perhaps I could do some interesting
database queries the next time it appears?

Sonar 2.10 on mysql, maven 3.0.3 with
org.codehaus.mojo:sonar-maven-plugin:2.0 (with lots of 2.10 dependencies),
centos 5.5.

Regards
Torbjörn


Freddy Mallet-3 wrote:
>
> The only known limitation which can lead to such issue is that Sonar
> doesn't support parallel runs on the SAME project :
>
> http://jira.codehaus.org/browse/SONAR-2761
>

--
View this message in context:
http://old.nabble.com/Sonar-2.11-Embedded-error%3A-PicoLifecycleException%3A-tp32771678p32929912.html
Sent from the Sonar user mailing list archive at Nabble.com.


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

  http://xircles.codehaus.org/manage_email





--
Używam klienta poczty Opera Mail: http://www.opera.com/mail/


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

  http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|

Re: Sonar 2.11 Embedded error: PicoLifecycleException:

Daniel Jeliński
Sorry for threadjacking :) I am using SQL Server and C# and already found  
out what was wrong in my case. See my other mail.

Regards,
Daniel

Dnia 09-12-2011 o 15:38:32 Freddy Mallet <[hidden email]>  
napisał(a):

> Hi Daniel, are you also using Oracle and Sonar 2.11 ?
> -----
> twitter.com/FreddyMallet
> Sonar for Continuous Inspection
>
>
>
> 2011/12/9 Daniel Jeliński <[hidden email]>
>
>> Hello Freddy,
>> I am facing the same problem and I am certain that no analyses have been
>> launched simultaneously. All analyses are done by a single Jenkins  
>> server
>> which is set to a single worker thread.
>>
>> Also, the problem is repetitive, that is after running the suggested
>> update I get a single successful analysis, after which the problem  
>> returns.
>>
>> Also, the second of the snapshots points to the first, that is,
>> parent_snapshot_id of the second row equals to id of the first row.
>>
>> Any ideas?
>>
>> Regards,
>> Daniel
>>
>>
>> Dnia 09-12-2011 o 14:09:08 Freddy Mallet <[hidden email]>
>> napisał(a):
>>
>>  Hi Torbjöm,
>>>
>>> I'm sorry to come back to my first suggestion but according to your  
>>> error
>>> message I'm really pretty sure that two Sonar analysis have been  
>>> launched
>>> almost simultaneously on the same project as there is only 263 ms  
>>> between
>>> the two snapshots on the project :
>>>
>>> Snapshot[resourceId=10533,**createdAt=*2011-11-01
>>> 21:03:28.094*,version=3.2.3-**SNAPSHOT,last=true,status=P,**
>>> scope=PRJ,path=<null>,depth=0,**qualifier=TRK,rootId=<null>,**
>>> parentId=<null>,rootProjectId=**10533,period1Mode=previous_**
>>> analysis,period2Mode=days,**period3Mode=days,period4Mode=<**
>>> null>,period5Mode=<null>,**period1Param=2011-10-31,**
>>> period2Param=5,period3Param=**30,period4Param=<null>,**
>>> period5Param=<null>,**period1Date=2011-10-31
>>>
>>> 21:03:23.338,period2Date=2011-**10-27 21:03:28.094,period3Date=2011-**
>>> 10-02
>>> 21:03:28.094,period4Date=<**null>,period5Date=<null>,id=**28598],
>>>
>>> Snapshot[resourceId=10533,**createdAt=*2011-11-01
>>> 21:03:28.259*,version=3.2.3-**SNAPSHOT,last=true,status=P,**
>>> scope=PRJ,path=<null>,depth=0,**qualifier=TRK,rootId=<null>,**
>>> parentId=<null>,rootProjectId=**10533,period1Mode=previous_**
>>> analysis,period2Mode=days,**period3Mode=days,period4Mode=<**
>>> null>,period5Mode=<null>,**period1Param=2011-10-31,**
>>> period2Param=5,period3Param=**30,period4Param=<null>,**
>>> period5Param=<null>,**period1Date=2011-10-31
>>>
>>> 21:03:23.338,period2Date=2011-**10-27 21:03:28.259,period3Date=2011-**
>>> 10-02
>>> 21:03:28.259,period4Date=<**null>,period5Date=<null>,id=**28599]
>>>
>>> -----
>>> twitter.com/FreddyMallet
>>> Sonar for Continuous Inspection
>>>
>>>
>>>
>>> On Wed, Dec 7, 2011 at 5:46 PM, Torbjörn Hultén
>>> <[hidden email]>**wrote:
>>>
>>>
>>>> I've been following this issue for quite some time and I do not think
>>>> this
>>>> is
>>>> the only circumstance under which it appears. We first installed Sonar
>>>> 2.7
>>>> and soon after upgraded to 2.7.1. I read that the issue should have  
>>>> been
>>>> solved in 2.8, but by the time we got around to update 2.10 had been
>>>> released and that is the version we are running at the moment.
>>>>
>>>> Today I "fixed" our database (again) by running the one-liner  
>>>> suggested
>>>> in
>>>> one of the related Jira issues.
>>>>
>>>> update snapshots old_snap, snapshots new_snap set old_snap.islast=0  
>>>> where
>>>> old_snap.islast=1 and new_snap.created_at > old_snap.created_at and
>>>> new_snap.project_id = old_snap.project_id and new_snap.islast=1
>>>>
>>>> This resulted in 58 rows being updated.
>>>>
>>>> The project in which the issue was noticed is a relatively new one
>>>> (created
>>>> post 2.10) and is relatively simple (i.e. no sub modules). The sonar
>>>> analysis is only performed by our Jenkins build server and the  
>>>> likelihood
>>>> of
>>>> anybody running it manually is very slim, let alone simultaneously.
>>>>
>>>> Is there anything I could do to help in trying to isolate the cause?  
>>>> It
>>>> is
>>>> intermittent and I haven't been able to find a pattern so far. I'm not
>>>> able
>>>> to disclose any actual data, but perhaps I could do some interesting
>>>> database queries the next time it appears?
>>>>
>>>> Sonar 2.10 on mysql, maven 3.0.3 with
>>>> org.codehaus.mojo:sonar-maven-**plugin:2.0 (with lots of 2.10
>>>> dependencies),
>>>> centos 5.5.
>>>>
>>>> Regards
>>>> Torbjörn
>>>>
>>>>
>>>> Freddy Mallet-3 wrote:
>>>> >
>>>> > The only known limitation which can lead to such issue is that Sonar
>>>> > doesn't support parallel runs on the SAME project :
>>>> >
>>>> >  
>>>> http://jira.codehaus.org/**browse/SONAR-2761<http://jira.codehaus.org/browse/SONAR-2761>
>>>> >
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Sonar-2.**11-Embedded-error%3A-**
>>>> PicoLifecycleException%3A-**tp32771678p32929912.html<http://old.nabble.com/Sonar-2.11-Embedded-error%3A-PicoLifecycleException%3A-tp32771678p32929912.html>
>>>> Sent from the Sonar user mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>   http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email>
>>>>
>>>>
>>>>
>>>>
>>
>> --
>> Używam klienta poczty Opera Mail: http://www.opera.com/mail/
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email>
>>
>>
>>


--
Używam klienta poczty Opera Mail: http://www.opera.com/mail/

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

    http://xircles.codehaus.org/manage_email