[
http://jira.codehaus.org/browse/MRM-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150946#action_150946
]
Maria Odea Ching commented on MRM-971:
--------------------------------------
I think the cause of this is that the execution of the repo task & database
task overlapped. There's a consumer set during repo scan which indexes the
artifact and then there's also the index-public-methods consumer (for indexing
java packages and public classes/methods) which is configured to be executed
during db scan.
I'm thinking if moving the index-public-methods consumer to the repo scanning
phase would solve this problem..
> ConsumerException while starting up Archiva
> -------------------------------------------
>
> Key: MRM-971
> URL: http://jira.codehaus.org/browse/MRM-971
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.1.1
> Environment: archiva running inside Tomcat
> Reporter: Sascha Hofer
> Fix For: 1.1.x
>
>
> after starting up archiva the logfile contains errors like the one below
> 2008-10-14 09:05:52,164 [pool-1-thread-1] WARN
> org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure -
> Unable to process artifact
> [com.cg.g3his:pac.pam.api:jar:tests:0.0.1-20081014.060438-731] with consumer
> [index-public-methods]
> org.apache.maven.archiva.consumers.ConsumerException: Error encountered while
> adding artifact to index: Error updating index: Lock obtain timed out: [EMAIL
> PROTECTED]:\G3ROOT\mvn-repositories\archiva\cg.snapshots\.index\bytecode\write.lock
> at
> org.apache.maven.archiva.consumers.lucene.IndexJavaPublicMethodsConsumer.processArchivaArtifact(IndexJavaPublicMethodsConsumer.java:162)
> at
> org.apache.maven.archiva.database.updater.ProcessArchivaArtifactClosure.execute(ProcessArchivaArtifactClosure.java:50)
> at
> org.apache.commons.collections.CollectionUtils.forAllDo(CollectionUtils.java:388)
> at
> org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateUnprocessed(JdoDatabaseUpdater.java:154)
> at
> org.apache.maven.archiva.database.updater.JdoDatabaseUpdater.updateAllUnprocessed(JdoDatabaseUpdater.java:88)
> at
> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor.executeTask(ArchivaDatabaseUpdateTaskExecutor.java:70)
> at
> org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
> at
> edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
> at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
