)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Monday, February 11, 2008 12:57 PM
To: archiva-users@maven.apache.org
Subject: RE: repository purge isn't
I am running the standalone archiva and I have about 4 managed
repositories (including a proxy repo), and about 6 or 7 remote
repositories. I create a single proxy connector to all of the remote
repositories and changed my settings.xml to be a mirrorOf *. Currently,
I only have my Continuous
. We have 5 repositories and
about 6 remote repositories and we too are using the standalone product
and nearly all consumers.
What platform are you running on?
Eric
On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote:
I am running the standalone archiva and I have about 4 managed
no answers.
i eventually had to reinstall fresh to get around it but all works great
now.
FYI, we're on RHEL 4 update 4 as well.
Eric
On Fri, 2008-02-22 at 13:01 -0800, Jason Chaffee wrote:
I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at
least 6 times in the last two weeks
of days
We use:
0 30 2 * * ? - daily at 2:30 am
0 30 * * * ? - every 30 mins
The default out of the box shouldn't be an issue I wouldn't think. How
large are your repos?
Ours:
344Mjasper
332Kplugins
203Mproxied
107Mreleases
239Msnapshots
On Fri, 2008-02-22 at 13:28 -0800, Jason
in the bug tracking system that you feel
need attention?
Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi
Archiva overall open (non-future) bugs - http://urltea.com/2rqj
- Joakim
Jason Chaffee wrote:
Is there an ETA on the 1.0.2 release? I would really like to get
the fixes so far, or if more
investigation is needed.
Thanks,
Brett
On 25/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
Actually, I misspoke. I checked the logs again today and saw the NPE
during the database scanning. I am not sure what is going on because
I
didn't change any
?
- Brett
On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I think it has something to do with the log file reaching 2 GB in
size.
I couldn't even restart it until I remove the log files.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26
/log4j:configuration
Brett Porter wrote:
On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I have not. Is that configured in the plexus.xml?
No, log4j.xml - but it seems like the problem is just too many
exception messages? Is that what is filling the log so fast?
- Brett
It appears that archiva consumers modify the repository and change
timestamps to GMT. The next time I try to deploy an artifact it starts
over at build number 1, even though the previous build number was 30.
I am not sure what I can do to resolve this either in Archvia or maven??
to the list and it ran through the unit tests on the branch
just fine.
- Brett
On 14/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I am using the SNAPSHOT that Brett provided, and MRM-691 seems to be
fixed, but not MRM-632 as I am still seeing that for some artifacts.
-Original Message
?
Cheers,
Brett
On 14/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
Here is a snippet from the log file:
431177909 [pool-2-thread-1] ERROR
org.apache.maven.archiva.repository.scanner.RepositoryScanner:default
-
Consumer [repository-purge] had an error when processing file
Here is my archiva.xml, in case it provides any other info.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 9:33 PM
To: archiva-users@maven.apache.org
Subject: RE: archiva-1.0.2 eta?
I was using the metdata-updater at one time, but we
: archiva-1.0.2 eta?
On 20/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I just sent my archiva.xml, which should give you a complete picture.
Ok, so I will file a new issue, but removing *.xml from your artifacts
list temporarily will fix the exception problems you were having with
the latest code
FYI, I have noticed something similar after Archiva is up for a while
and I thought it was related to my other consumer issues so I didn't
mention it. One possibility to consider is the difference of Archiva
being used as both a proxy and repository manager as opposed to just a
proxy.
Anyway, I
Also, if the artifact is in the local cache and this failure happens,
shouldn't is simply log it and then return the cached artifact?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 6:29 AM
To: archiva-users@maven.apache.org
Subject: Re:
correct the plugin group metadata).
- Brett
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
According to the documentation the metadata-updater will do the
following:
metadata-updater - Updates artifact metadata files depending on the
content of the repository.
I have been testing
-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 3:54 PM
To: archiva-users@maven.apache.org
Subject: Re: metadata -updater does not appear to be working!
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I will file it today. Is there any chance of getting
deleting files.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 4:34 PM
To: archiva-users@maven.apache.org
Subject: Re: metadata -updater does not appear to be working!
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
1) touching the old
Gomez [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 9:50 AM
To: archiva-users@maven.apache.org
Subject: Re: too many open files with 1.0.2
I see that also but it was releated to a problem with Tomcat 6.x and
libtcnative.
Is it your setting ?
2008/4/11, Jason Chaffee [EMAIL PROTECTED
20 matches
Mail list logo
