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

Mario Parra commented on MRM-1418:
----------------------------------

I already asked the guy that has access to MySQL logs, let's see what can we 
find there.

In the mean time, I found a weird behavior, because the number of rows of that 
table start to bounce until it get to 2 rows. For example:

1. Originally it has 1818 rows
2. When the issue start to happen it decreases to 1214
3. But then, it is 1624
4. Then 1106
5. Then 1320
6. Then 488
and it keeps running like that until I have 2 rows, the same rows that never 
get deleted, which are for the only artifact I have added after the migration 
to Archiva 1.3.1

Couldn't be something about the .index or .indexer files I have inside of the 
repositories?


> 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