Also there is an annoying memory leak. i need to restart continumm each second or third day :(
On 27/03/06, Kaare Nilsen <[EMAIL PROTECTED]> wrote: > Hi been using the RC SNAPSHOT, and i do not feel it is ready for > production yet. To often when i look in the list something has been > broken, not of problems in the app that is being build, but in the > continuum itself. here is the latest one. > > problem with the 1.0.3 RC Snapshot : > javax.jdo.JDODataStoreException: Transaction failed to commit > at > org.jpox.NonmanagedTransaction.rollback(NonmanagedTransaction.java:558) > at > org.apache.maven.continuum.store.JdoContinuumStore.rollback(JdoContinuumStore.java:577) > at > org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java:260) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult(DefaultBuildController.java:434) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:177) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) > NestedThrowablesStackTrace: > SQL Exception: No current connection. > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown > Source) > at org.apache.derby.impl.jdbc.Util.noCurrentConnection(Unknown Source) > at > org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedConnection.rollback(Unknown Source) > at > org.jpox.NonmanagedTransaction.rollback(NonmanagedTransaction.java:535) > at > org.apache.maven.continuum.store.JdoContinuumStore.rollback(JdoContinuumStore.java:577) > at > org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java:260) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult(DefaultBuildController.java:434) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:177) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) > > On 24/03/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > > > > Yann Le Du a écrit : > > > Done, CONTINUUM-637 and CONTINUUM-638 > > > > > > Actually, CONTINUUM-638 only happens with parent/module - not with > > > dependency. > > > > I'll look at it later. > > > > > > > > BTW, I had a question about migration to 1.0.3. Can we keep old > > > build-output-directory and working-directory or do we have to re-create > > > them > > > from scratch ? I believe you wrote about a migration tool, but I can't > > > find > > > the thread anymore... > > > > It isn't a tool. I'll write migration documentation in few days. You can > > keep build-output-directory > > and working-directory if you configure continuum to use them. > > You can keep too the database if you copy old database un der > > $NEW_CONTINUUM/apps/continuum/ > > > > Emmanuel > > > > > > On 3/24/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > > > >> > > >> > > >>Yann Le Du a écrit : > > >> > > >>>Hi Emmanuel, > > >>> > > >>>I just tried 20060324.020000 and my problem about 2 build definitions > > >> > > >>with > > >> > > >>>the same schedule is seemlingly still happening. But now, only the > > >> > > >>*first* > > >> > > >>>definition is executed. > > >>> > > >>>You can try with this simple example : > > >>>Definition 1 : clean site-deploy - DEFAULT_SCHEDULE > > >>>Definition 2 : clean install - DEFAULT_SCHEDULE (default buld > > >> > > >>definition) > > >> > > >>>Only Definition 1 is executed. > > >> > > >>You're right, the second is launched but without changes, it doesn't run > > >>the build. I'll look at it > > >> > > >> > > >>>I also noticed antoher thing. You have projects A and B in Continuum. B > > >>>depends on A (in my case, A is the parent of B). B has a build > > >> > > >>definition > > >> > > >>>for a given schedule, but A has *no* build definition for this schedule. > > >>>Then B build won't be executed, probably because it waits for A > > >> > > >>execution > > >> > > >>>first - which won't happen. > > >> > > >>hmm, strange. I'll look at it. > > >> > > >>Can you file two issues for these problems (with 1.0.3 fixed version)? > > >> > > >>Emmanuel > > >> > > >>>Don't hesitate if you need more details. > > >>> > > >>>On 3/24/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>>>I have this error only when i shutdown continuum. I fixed it. > > >>>> > > >>>>Emmanuel > > >>>> > > >>>>Olivier Lamy a écrit : > > >>>> > > >>>> > > >>>>>Not reproduce (strange ?). > > >>>>>Sorry for noise. > > >>>>> > > >>>>>- Olivier > > >>>>> > > >>>>>-----Message d'origine----- > > >>>>>De : Olivier Lamy [mailto:[EMAIL PROTECTED] > > >>>>>Envoyé : vendredi 24 mars 2006 10:26 > > >>>>>À : '[email protected]' > > >>>>>Objet : RE : Re: RE : Continuum 1.0.3 RC require some tester > > >>>>> > > >>>>> > > >>>>>Hi, > > >>>>>Thanks emmanuel. > > >>>>> > > >>>>>Note the env : > > >>>>>- solaris : uname -a > 5.9 Generic_118558-13 sun4u sparc > > >>>>>SUNW,Sun-Fire-V240 > > >>>>>- JAVA_HOME -> j2sdk1.4.2_04 > > >>>>>- using $CONTINUUM/bin/plexus.sh (not using wrapper) > > >>>>>- snapshot 20060317.073000 > > >>>>> > > >>>>>I will try today to reproduce it (I need to way the next schedule 11H00 > > >>>>>Paris Time, suspens ;-) ) > > >>>>> > > >>>>>- Olivier > > >>>>> > > >>>>> > > >>>>> > > >>>>>-----Message d'origine----- > > >>>>>De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > > >>>>>Envoyé : vendredi 24 mars 2006 00:10 > > >>>>>À : [email protected] > > >>>>>Objet : Re: Re: RE : Continuum 1.0.3 RC require some tester > > >>>>> > > >>>>> > > >>>>>Yann, it's fixed now, all build definitions on the same schedule are > > >>>>>executed. > > >>>>> > > >>>>>Olivier, I can't reproduce your problem. > > >>>>> > > >>>>>Emmanuel > > >>>>> > > >>>>>Yann Le Du a écrit : > > >>>>> > > >>>>> > > >>>>> > > >>>>>>Everything is working fine for me, especially > > >>>>>>http://jira.codehaus.org/browse/CONTINUUM-577 > > >>>>>> > > >>>>>>I fail to reproduce Olivier's problem, either with 20060316.173001 or > > >>>>>>20060317.073000 . Only one of both definitions is executed (the last > > >>>>>>one in the list), but Continuum doesn't stop. > > >>>>>> > > >>>>>>Big thanks for this new version ! > > >>>>>> > > >>>>>>- Yann > > >>>>>> > > >>>>>>On 3/20/06, Olivier Lamy <[EMAIL PROTECTED]> wrote: > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>>In fact not so good. > > >>>>>>>Log : > > >>>>>>>2006-03-18 09:40:52,260 [Thread-7] ERROR > > >>>>>>>org.codehaus.plexus.summit.pull.PullService - Problem disp osing > > >>>>>>>global tools: java.util.ConcurrentModificationException > > >>>>>>> at java.util.HashMap$HashIterator.nextEntry (HashMap.java:782) > > >>>>>>> at java.util.HashMap$KeyIterator.next(HashMap.java:818) > > >>>>>>> at > > >>>>>>>org.codehaus.plexus.summit.pull.DefaultPullService.disposeGlobalTools > > >> > > >>( > > >> > > >>>>>De > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>fault > > >>>>>>> > > >>>>>>>This stop continuum. > > >>>>>>>Simple test with two build definition on the same project and with > > >> > > >>the > > >> > > >>>>>>>same schedule (I know not a normal use case ;-) but it failed). > > >>>>>>> > > >>>>>>>Snapshot : continuum-20060317.073000 > > >>>>>>> > > >>>>>>>- Olivier > > >>>>>>> > > >>>>>>> > > >>>>>>>-----Message d'origine----- > > >>>>>>>De : Olivier Lamy [mailto: [EMAIL PROTECTED] > > >>>>>>>Envoyé : vendredi 17 mars 2006 17:20 > > >>>>>>>À : '[email protected]' > > >>>>>>>Objet : RE : Continuum 1.0.3 RC require some tester > > >>>>>>> > > >>>>>>> > > >>>>>>>Hi, > > >>>>>>>I have made some tests and it looks ok. > > >>>>>>>Especially the issue concerning reading $HOME/.m2/settings.xml > > >>>>>>>(http://jira.codehaus.org/browse/CONTINUUM-590 ) > > >>>>>>> > > >>>>>>>Good job. > > >>>>>>>You don't have to wait maven 2.0.3 release ? > > >>>>>>> > > >>>>>>>- Olivier > > >>>>>>> > > >>>>>>>PS : I'm not an orange fan but no problem ;-) > > >>>>>>> > > >>>>>>>-----Message d'origine----- > > >>>>>>>De : Emmanuel Venisse [mailto: [EMAIL PROTECTED] > > >>>>>>>Envoyé : jeudi 16 mars 2006 22:33 > > >>>>>>>À : [email protected] > > >>>>>>>Objet : Continuum 1.0.3 RC require some tester > > >>>>>>> > > >>>>>>> > > >>>>>>>Hi, > > >>>>>>> > > >>>>>>>I think it's time to release Continuum 1.0.3. This release will > > >>>>>>>incorporate 65 issues, including some critical fixes. The full > > >> > > >>listing > > >> > > >>>>> > > >>>>>>>of fixes can be found here: > > >>>>>>> > > >>>>>>> > > >> > > >>http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&style > > >> > > >>>>>>>Na > > >>>>>>>me=Html&version=12330 > > >>>>>>> > > >>>>>>>If you're interested, you can take the current release candidate for > > >> > > >>a > > >> > > >>>>>>>test drive. The RC tarball is at: > > >>>>>>> > > >>>>>>> > > >> > > >>http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0 > > >> > > >>>>>>>.x< > > >> > > >>http://maven.zones.apache.org/%7Econtinuum/builds/branches/continuu > > >> > > >>>>>>>m-1.0.x> > > >>>>>>>/continuum-20060316.173001.tar.gz > > >>>>>>> > > >>>>>>>Cheers, > > >>>>>>> > > >>>>>>>Emmanuel > > >>>>>>> > > >>>>>>> > > >>>>>>> > > >>>>>>>This e-mail, any attachments and the information contained therein > > >>>>>>>("this > > >>>>>>>message") are confidential and intended solely for the use of the > > >>>>>>>addressee(s). If you have received this message in error please send > > >>>>> > > >>>>>it back > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>to the sender and delete it. Unauthorized publication, use, > > >>>>> > > >>>>>dissemination or > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>disclosure of this message, either in whole or in part is strictly > > >>>>>>>prohibited. > > >> > > >>>>>>>********************************************************************** > > >>>>>>>Ce message électronique et tous les fichiers joints ainsi que les > > >>>>>>>informations contenues dans ce message ( ci après "le message" ), > > >> > > >>sont > > >> > > >>>>>>>confidentiels et destinés exclusivement à l'usage de la personne à > > >>>>> > > >>>>>laquelle > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>ils sont adressés. Si vous avez reçu ce message par erreur, merci de > > >>>>> > > >>>>>le > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>renvoyer à son émetteur et de le détruire. Toutes diffusion, > > >>>>> > > >>>>>publication, > > >>>>> > > >>>>> > > >>>>> > > >>>>>>>totale ou partielle ou divulgation sous quelque forme que se soit non > > >>>>>>>expressément autorisées de ce message, sont interdites. > > >> > > >>>>>>>********************************************************************** > > >>>>>>> > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>> > > >>>>>This e-mail, any attachments and the information contained therein > > >>>> > > >>>>("this message") are confidential and intended solely for the use of the > > >>>>addressee(s). If you have received this message in error please send it > > >> > > >>back > > >> > > >>>>to the sender and delete it. Unauthorized publication, use, > > >> > > >>dissemination or > > >> > > >>>>disclosure of this message, either in whole or in part is strictly > > >>>>prohibited. > > >>>> > > >> > > >>>>-------------------------------------------------------------------------------------------------------------- > > >>>> > > >>>> > > >>>>>Ce message électronique et tous les fichiers joints ainsi que les > > >>>> > > >>>>informations contenues dans ce message ( ci après "le message" ), sont > > >>>>confidentiels et destinés exclusivement à l'usage de la personne à > > >> > > >>laquelle > > >> > > >>>>ils sont adressés. Si vous avez reçu ce message par erreur, merci de le > > >>>>renvoyer à son émetteur et de le détruire. Toutes diffusion, > > >> > > >>publication, > > >> > > >>>>totale ou partielle ou divulgation sous quelque forme que se soit non > > >>>>expressément autorisées de ce message, sont interdites. > > >>>> > > >> > > >>>>------------------------------------------------------------------------------------------------------------- > > >>>> > > >>>> > > >>>>> > > >>>>> > > >> > > > > > > > >
