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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 >>>>> >>>>> >>>> >>> >
