[
http://jira.codehaus.org/browse/MRM-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233965#action_233965
]
Mario Parra commented on MRM-1418:
----------------------------------
Another weird stuff... about the database consumers.
In Archiva web application it shows only 1 "Database - Unprocessed Artifacts
Scanning" which is "update-db-project".
But on the documentation it mentions that it should show 6 Unprocessed
Artifacts Consumers:
* validate-repository-metadata - Verifies repository metadata files against
database.
* index-archive-toc - Indexes the archiva table of contents for full text
search.
* index-artifact - Indexes the artifact for the 'Find Artifact'
functionality.
* update-db-project - Gets the details of the artifact from the pom and
saves it into the database (as a project model)
* index-public-methods - Indexes the java public methods for full text
search.
* update-db-bytecode-stats - Updates database with java bytecode stats.
Is this some miss-configuration?
> Archiva Repostories Index is dissapearing with no reason
> --------------------------------------------------------
>
> Key: MRM-1418
> URL: http://jira.codehaus.org/browse/MRM-1418
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 1.3.1
> Environment: Archiva 1.3.1
> Linux RedHat
> Apache maven 2.0.9
> Continuum 1.3.6
> Reporter: Mario Parra
>
> After I migrated from Archiva 1.2.2 to Archiva 1.3.1 the repositories that
> already existed on my previous installation of Archiva are dissapearing from
> the Archiva browser index.
> Everyday I need to do a re-scan of the repositories to have the repositories
> and artifacts listed again.
> I have looked at the logs at the same time the repositories are been erased
> from the index but there is no output there.
> I have also tried to identify if there is a cronjob or something that causes
> this behavior but haven't find anything and also the time when this happens
> is random.
> Please Help.
> Thanks
--
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
