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

Reply via email to