Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 13225 invoked from network); 30 Mar 2006 17:03:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Mar 2006 17:03:28 -0000 Received: (qmail 14762 invoked by uid 500); 30 Mar 2006 17:03:28 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 14524 invoked by uid 500); 30 Mar 2006 17:03:27 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 14511 invoked by uid 99); 30 Mar 2006 17:03:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Mar 2006 09:03:27 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [62.193.206.22] (HELO rs-so-c1.amenworld.com) (62.193.206.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Mar 2006 09:03:26 -0800 Received: from localhost (localhost [127.0.0.1]) by rs-so-c1.amenworld.com (Postfix) with ESMTP id 986286F9C4 for ; Thu, 30 Mar 2006 19:02:42 +0200 (CEST) Received: from rs-so-c1.amenworld.com ([127.0.0.1]) by localhost (rs-so-c1.amenworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18011-01-10 for ; Thu, 30 Mar 2006 19:02:27 +0200 (CEST) Received: from webmail9.amenworld.com (webmail9.amenworld.com [62.193.206.9]) by rs-so-c1.amenworld.com (Postfix) with SMTP id 2FE717041B for ; Thu, 30 Mar 2006 14:21:48 +0200 (CEST) Received: (qmail 6323 invoked from network); 30 Mar 2006 12:22:13 -0000 Received: from 90.20.99-84.rev.gaoland.net (HELO ?127.0.0.1?) (84.99.20.90) by 0 with SMTP; 30 Mar 2006 12:22:13 -0000 Message-ID: <442BCD69.4030409@venisse.net> Date: Thu, 30 Mar 2006 14:22:01 +0200 From: Emmanuel Venisse User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: fr, en MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: RE : Re: RE : Continuum 1.0.3 RC require some tester References: <002401c64f2a$1b4e39d0$cad9c839@eu.accor.net> <4423DAEC.4050008@venisse.net> <117228810603240500o2cdd9647m81a4a9bd5a4c6f15@mail.gmail.com> <4423F2E5.9050200@venisse.net> <117228810603240652m646cd9f0ia15b9ff73b51aee7@mail.gmail.com> <442432AA.7020808@venisse.net> <58ca838c0603270043q7dd26bf5x@mail.gmail.com> <58ca838c0603300415m31c2c59dle2397088ce53da98@mail.gmail.com> <58ca838c0603300415j2dbbf2d5g4ee32cdeb1859894@mail.gmail.com> In-Reply-To: <58ca838c0603300415j2dbbf2d5g4ee32cdeb1859894@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Amavis at rs-so-c1.amenworld.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N icons in sumary page are fixed. For the memory leak, it seems it's a problem with jpox rc1. I found some issues about memory leak in their jira. Emmanuel Kaare Nilsen a �crit : > And sometimes the index page shows that builds have failed, but when > you look at the actual build results, it is fine > > On 30/03/06, Kaare Nilsen wrote: > >>Also there is an annoying memory leak. i need to restart continumm >>each second or third day :( >> >>On 27/03/06, Kaare Nilsen 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 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 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 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:olivier.lamy@accor.com] >>>>>>>>>Envoy� : vendredi 24 mars 2006 10:26 >>>>>>>>>� : 'continuum-users@maven.apache.org' >>>>>>>>>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:emmanuel@venisse.net] >>>>>>>>>Envoy� : vendredi 24 mars 2006 00:10 >>>>>>>>>� : continuum-users@maven.apache.org >>>>>>>>>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 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: olivier.lamy@accor.com] >>>>>>>>>>>Envoy� : vendredi 17 mars 2006 17:20 >>>>>>>>>>>� : 'continuum-users@maven.apache.org' >>>>>>>>>>>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: emmanuel@venisse.net] >>>>>>>>>>>Envoy� : jeudi 16 mars 2006 22:33 >>>>>>>>>>>� : continuum-users@maven.apache.org >>>>>>>>>>>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. >>>>>>>> >>>>>> >>>>>>>>------------------------------------------------------------------------------------------------------------- >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>> > > >