[
https://issues.apache.org/jira/browse/MRM-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532280#comment-14532280
]
Konrad Wulf commented on MRM-1882:
----------------------------------
thanks for the hint: yes, the repository-purge consumer wasn't activated. I've
turned it on and then it really executed the task. So it seems that it is just
that you should mention this activation of the repository-purge consumer in the
docs...
But it seems I've broken the index scanning feature before by removing the
contents of the snapshot manually via command line. Seems it was not a good
idea to also remove the .indexer folder... Is there an easy way to repair this?
Perhaps tell Lucene to do an initial scan? - that would be really helpful...
Here's the tomcat log snippet that I got when a) triggering the index scanning
via the web ui and b) after switching on the repository purge consumer:
10:30:00.107 [pool-12-thread-1] ERROR
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor
- Error executing task
org.apache.archiva.redback.components.taskqueue.execution.TaskExecutionException:
Error scan repository AbstractRepository{id='snapshots', name='Archiva Managed
Snapshot Repository', l
ayout='default',
indexDirectory='/var/lib/tomcat7/repositories/snapshots/.indexer',
description='null'}ManagedRepository{location='/var/lib/tomcat7/repositories/snapshots',
snapshots=t
rue, releases=false, blockRedeployments=false, cronExpression='0 0/30 * * * ?',
stagingRepository=null, scanned=true, daysOlder=3, retentionCount=0,
deleteReleasedSnapshots=false, stag
eRepoNeeded=false, resetStats=false, skipPackedIndexCreation=false}
at
org.apache.archiva.scheduler.indexing.ArchivaIndexingTaskExecutor.executeTask(ArchivaIndexingTaskExecutor.java:119)
~[archiva-scheduler-indexing-2.2.0.jar:?]
at
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:117)
[spring-taskqueue-2.1.jar:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[?:1.7.0_79]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[?:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[?:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [?:1.7.0_79]
Caused by: java.io.IOException: Error scanning context snapshots:
org.apache.lucene.store.NoSuchDirectoryException: directory
'/var/lib/tomcat7/repositories/snapshots/.indexer' does no
t exist
at
org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:297)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:236)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.archiva.scheduler.indexing.ArchivaIndexingTaskExecutor.executeTask(ArchivaIndexingTaskExecutor.java:112)
~[archiva-scheduler-indexing-2.2.0.jar:?]
... 6 more
Caused by: org.apache.lucene.store.NoSuchDirectoryException: directory
'/var/lib/tomcat7/repositories/snapshots/.indexer' does not exist
at org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:218)
~[lucene-core-3.6.2.jar:3.6.2 1423725 - rmuir - 2012-12-18 19:45:40]
at org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:241)
~[lucene-core-3.6.2.jar:3.6.2 1423725 - rmuir - 2012-12-18 19:45:40]
at
org.apache.maven.index.context.DefaultIndexingContext.deleteIndexFiles(DefaultIndexingContext.java:333)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.context.DefaultIndexingContext.replace(DefaultIndexingContext.java:570)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:293)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultNexusIndexer.scan(DefaultNexusIndexer.java:236)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.archiva.scheduler.indexing.ArchivaIndexingTaskExecutor.executeTask(ArchivaIndexingTaskExecutor.java:112)
~[archiva-scheduler-indexing-2.2.0.jar:?]
... 6 more
10:32:22.519 [Thread-33] ERROR
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor
- Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
~[?:1.7.0_79]
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
~[?:1.7.0_79]
at
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.waitForTask(ThreadedTaskQueueExecutor.java:160)
~[spring-taskqueue-2.1.j
ar:?]
at
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:128)
[spring-taskqueue-2.1.jar:?]
Caused by: java.lang.NullPointerException
at
org.apache.maven.index.context.DefaultIndexingContext.acquireIndexSearcher(DefaultIndexingContext.java:498)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultSearchEngine.searchFlat(DefaultSearchEngine.java:135)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultSearchEngine.searchFlatPaged(DefaultSearchEngine.java:93)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultSearchEngine.forceSearchFlatPaged(DefaultSearchEngine.java:83)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultIndexer.searchFlat(DefaultIndexer.java:144)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.maven.index.DefaultNexusIndexer.searchFlat(DefaultNexusIndexer.java:373)
~[indexer-core-5.1.1.jar:5.1.1]
at
org.apache.archiva.scheduler.indexing.ArchivaIndexingTaskExecutor.executeTask(ArchivaIndexingTaskExecutor.java:193)
~[archiva-scheduler-indexing-2.2.0.jar:?]
at
org.apache.archiva.redback.components.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:117)
~[spring-taskqueue-2.1.jar:?]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
~[?:1.7.0_79]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
~[?:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
~[?:1.7.0_79]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
~[?:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) ~[?:1.7.0_79]
> automatical deletion of snapshot artifacts not working
> -------------------------------------------------------
>
> Key: MRM-1882
> URL: https://issues.apache.org/jira/browse/MRM-1882
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 2.2.0
> Environment: Archiva 2.2.0 webapp deployed on Tomcat 7:
> --------------------------------------------------------
> Server version: Apache Tomcat/7.0.26
> Server built: Apr 1 2013 08:32:04
> Server number: 7.0.26.0
> OS Name: Linux
> OS Version: 3.2.0-55-generic
> Architecture: amd64
> JVM Version: 1.7.0_76-b13
> JVM Vendor: Oracle Corporation
> OS details:
> Distributor ID: Ubuntu
> Description: Ubuntu 12.04.5 LTS
> Release: 12.04
> Codename: precise
> Hardware details:
> 64-bit OS
> CPU: 6 * "Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz"
> RAM 8 GB (DIMM DRAM EDO)
> Reporter: Konrad Wulf
>
> In 'Repositories Administration' (web admin interface), when I edit the
> snapshot repository settings as follows:
> Cron Expression: 0 0,30 * * * ?
> Days Older: 15
> Retention Count: 2
> The number of versions held of a given snapshot artifact is 4, both after
> waiting for one day and after a new snapshot deployment. My understanding is
> that with the given setting it should be 2 instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
