From dev-return-8161-apmail-continuum-dev-archive=continuum.apache.org@continuum.apache.org Fri May 29 09:16:03 2009 Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 83695 invoked from network); 29 May 2009 09:16:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 May 2009 09:16:03 -0000 Received: (qmail 87247 invoked by uid 500); 29 May 2009 09:16:16 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 87177 invoked by uid 500); 29 May 2009 09:16:16 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 87167 invoked by uid 99); 29 May 2009 09:16:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 09:16:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of emmanuel.venisse@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-fx0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 May 2009 09:16:05 +0000 Received: by fxm24 with SMTP id 24so6372661fxm.2 for ; Fri, 29 May 2009 02:15:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=B5NFMBTdgJdqOHVuR+srwsEfiSgxaqDG8JBWFZSVmiU=; b=fknzgq3EBbQrXi8Je2drTBMeZyAf+tfZu9eUWhv/dKfvrFAj0sIypYmBa0Rrs38gW5 orwIEfR/SR4kzlroSYXpxSsHb/XRjy+/R5fET5TjMH5nmzdUWFsRJLZVfLqa6riOdokG 18UufOg+GIhnwNiiJY7dYhaM/CivhJVi+kk+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=fXCeArejn87hRw4m4o5c9Yq5/jnnj/6828bfzpWhJzyYad9jF8WpzDkp9voPOjhSlr 7aAORPOpa+e6Ykpn7f7535hZbjp844lRBqqjnHpLQg9+vaSmtpO0RbScf9mCIqPtgZF2 /G8xQ59QIK8adU5shcSG75R7Us+jlBoSP1vNE= MIME-Version: 1.0 Received: by 10.223.126.145 with SMTP id c17mr1869471fas.16.1243588545148; Fri, 29 May 2009 02:15:45 -0700 (PDT) In-Reply-To: <2B6DE053-3D9E-4222-A4E4-C557D39DFC7F@apache.org> References: <0E6DE2BD-727C-4C81-9C85-D475FC3C1E7C@apache.org> <2B6DE053-3D9E-4222-A4E4-C557D39DFC7F@apache.org> Date: Fri, 29 May 2009 11:15:45 +0200 Message-ID: Subject: Re: stability problems on vmbuild From: Emmanuel Venisse To: dev@continuum.apache.org Content-Type: multipart/alternative; boundary=001636c5a7367af621046b098507 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a7367af621046b098507 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I fixed it in plexus-utils in r.8235 I see in svn logs of plexus-utils that 1.5.10 was released yesterday but on central repo, it was deployed 3 days ago( http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.10/ ). Is it a problem with the date on central repo or is it the wrong artifact? So I don't know if the artifact on central repo contains or not my fix and the sources jar is wrong :-( Emmanuel On Fri, May 29, 2009 at 7:02 AM, Brett Porter wrote: > I haven't seen the commit - what's required? > > If you could get it to the point the 1.3.x branch builds with the right > thing I'm happy to do the vmbuild upgrade. > > > On 29/05/2009, at 2:58 PM, Emmanuel Venisse wrote: > > I fixed plexus-utils. Can you test it on vmbuild to see if it is ok? >> I tested it locally with my Continuum and open files seems to be stable >> >> On 5/28/09, Emmanuel Venisse wrote: >> >>> For Archiva, we use actually in Continuum an old version, it would be >>> good to upgrade it. >>> >>> The issue can be in plexus-util too: >>> http://jira.codehaus.org/browse/PLXCOMP-99 >>> >>> Emmanuel >>> >>> On 5/27/09, Emmanuel Venisse wrote: >>> >>>> I started to look at it and fixed locally some of them in Continuum but >>>> they >>>> aren't new so I don't think my fixes will be enough. >>>> I think the issue is in Archiva but need some investigations. >>>> >>>> Emmanuel >>>> >>>> On Wed, May 27, 2009 at 7:32 AM, Brett Porter wrote: >>>> >>>> One of the things to take into consideration for the 1.3.x GA release >>>>> is >>>>> the stability problems we've had since upgrading on vmbuild. >>>>> >>>>> I noted it had gone down today due to "too many open files" (which >>>>> showed >>>>> up as a database error saying it couldn't be found - Derby confused me >>>>> at >>>>> first :) >>>>> >>>>> There have been similar reports recently against Archiva - but it >>>>> wasn't >>>>> present in previous versions of Continuum. Is it possible that it is >>>>> something new in Redback (we're not using LDAP), a different JDO >>>>> configuration, or perhaps the shared Archiva purge scanners that might >>>>> be >>>>> causing this? >>>>> >>>>> Before restarting next time I'll run an lsof to see what is happening. >>>>> >>>>> - Brett >>>>> >>>>> >>>> >>> > --001636c5a7367af621046b098507--