« Return to Thread: deleted entity passed to persist

Re: deleted entity passed to persist

by Olivier Gaudin-2 :: Rate this Message:

Reply to Author | View in Thread

Strange issue you are having...

Sonar does not need scm as such to function, it is only information that get displayed on the dashboard.

I don't know you environment, but I do not believe very much in your top theory :-) Why would there be a conflict between scm and Sonar ? I simply think that the conditions of the crash have been clean by the fact you rebuilt mysql.

To rebuild missing historical data, you should be able to use historical data injection : http://docs.codehaus.org/display/SONAR/Advanced+parameters

To try to understand beeter your issue, could you try to provide the following info ?
- do you run Sonar at every commit in SCM ?
- do you combine Sonar with mvn release goal ?
- would you be able to find scm infos before and after the crash ?

Thanks

Olivier


On Mon, Jul 6, 2009 at 5:44 PM, harshavsn <harsha.sri-narayana@...> wrote:

I recreated the mysql database from scratch and ran sonar again.  Now it
works.

My top theory explaining why....

I recently took down the sonar server for a few hours.  I think in that
time, other developers continued to make commits to the subversion server.
When sonar came back online, there was a database conflict between it's
internal data about this project FooBar and the subversion copy of FooBar.

The real problem is that we've lost all the collected historical data.  If
this problem arises everytime we take the sonar server down, I suspect my
managers are going to ditch my work on it.
--
View this message in context: http://www.nabble.com/deleted-entity-passed-to-persist-tp24271089p24357877.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



 « Return to Thread: deleted entity passed to persist