[ 
http://jira.codehaus.org/browse/MRM-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232879#action_232879
 ] 

Brett Porter commented on MRM-1418:
-----------------------------------

the only reason it would be cleaned is:
- if Archiva scans and finds the artifacts no longer on the disk
- if Archiva is configured to purge the repository of certain snapshots and 
deletes them from both

In both cases, this would correlate to the files not being on the disk, and not 
coming back afterwards. It sounds more like an external process affecting the 
MySQL database - has any such thing been set up? Do you have any logging on the 
database?

If you continue to suspect Archiva, you can change log4j.xml to increase 
debugging around the RDBMS and SQL level to see if any delete commands appear 
in the logs (it is very verbose though!)

> 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

        

Reply via email to