Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <28981594.post@talk.nabble.com>
Date: Thu, 24 Jun 2010 04:44:51 -0700 (PDT)
From: leahpar <raphael.petit@free.fr>
To: users@archiva.apache.org
Subject: Re: Archiva CPU Usage
In-Reply-To: <D1390C7B1724B349BD44B9A7E5DEE06101ECE9A4@OTWLMX06.opentext.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <D1390C7B1724B349BD44B9A7E5DEE06101ECE9A4@OTWLMX06.opentext.net>


Bonjour,

I've been face with this issue in the past.
This following explanation may be wrong but in my case it seems that

In production Archiva runs on a window OS that host also a virus scanner
with very strict rules : it scans jar because they are recognized as zip
file.
Each time the nexus indexer create a temporary file
the scanner 'takes' it and sometimes the indexer fail

This leads to
1- the device cpu is quite high during indexing (it can go up to 100%)
2- the indexer fails so artifacts disappear and reappear later in the
browse/search

In test environment (win or linux) without all the 'enterprise security
tools' this does not occured.

Cordialement


Chris LeCompte wrote:
> 
> Has anyone else seen Archiva peg the CPU at 100% while indexing?  It
> looks like it's continually updating the nexus index files even when
> there are no new artifacts to index.  Is this normal?  Any ideas?  How
> can I view what tasks are currently scheduled, other than attaching a
> debugger?  Thanks.
> 
> Chris
> 
> 

-- 
View this message in context: http://old.nabble.com/Archiva-CPU-Usage-tp28965855p28981594.html
Sent from the archiva-users mailing list archive at Nabble.com.