ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bram Pouwelse <b...@pouwelse.com>
Subject Re: How to keep ace performance consistent
Date Wed, 08 Jan 2014 21:19:55 GMT
Hi Paul,

The deployment is automated using the rest interface. Sessions not being
closed would be my first guess but restarting Ace would close such
sessions? The performance is not much better after restarting the ace
server.

The version I'm currently using is trunk from 16-11-2013

Bram


2014/1/8 Paul Bakker <paul.bakker@luminis.eu>

> Hi Bram,
>
> Are you using the web user interface? The problem that you are experiencing
> is most probably related to sessions not being cleared. We are running
> completely without the UI (we scripted deployments) and that works without
> any problems after many deployments.
> Besides that, on which version of ACE are you running?
>
> Cheers,
>
> Paul
>
>
> On Wed, Jan 8, 2014 at 8:37 PM, Bram Pouwelse <bram@pouwelse.com> wrote:
>
> > Hi all,
> >
> > I have a question regarding performance of Ace, and most important part
> is
> > how to keep the performance consistent over time. Now we've automated
> > moving artifacts to Ace and converting bndrun configurations from
> bndtools
> > to features and distributions Ace has made it to production at our
> company.
> >
> > There is one little issue, the deployments from the Jenkins server to Ace
> > are becoming slower when we just started deployment took seconds now it's
> > over 10 minutes. Also ace seems to need more and more memory.
> >
> >
> > I've tried to change the deploymentversionlimit
> > in conf/org.apache.ace.client.repository.cfg to 5 instead of the default
> > value of -1 (unlimited) but after that change I get an exception that the
> > repository is busy [1] (even after 30 minutes of waiting).
> >
> >
> > Is limiting the deployment versions the way to get the performance back
> to
> > the level of when we just started using ace? and if so how can I resolve
> > the "repository is busy" problem
> >
> > Are there other configuration options that can improve performance?
> >
> >
> > Thanks!
> >
> > Bram
> >
> >
> > [1]
> > g! ws = (ace:cw)
> > $ws commit
> > gogo: ConversionException: java.lang.IllegalStateException: The
> repository
> > is currently busy, so no objects can be removed.
> > ---- Debugging information ----
> > message             : java.lang.IllegalStateException: The repository is
> > currently busy, so no objects can be removed.
> > cause-exception     : java.lang.IllegalArgumentException
> > cause-message       : java.lang.IllegalStateException: The repository is
> > currently busy, so no objects can be removed.
> > class               :
> > org.apache.ace.client.repository.impl.RepositorySerializer
> > required-type       :
> > org.apache.ace.client.repository.impl.RepositorySerializer
> > path                : /repository/deploymentversions/deploymentversion[8]
> > line number         : 19543
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message