You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Bob Walker (JIRA)" <ji...@codehaus.org> on 2009/02/05 11:13:19 UTC
[jira] Created: (MRM-1078) SQL Server database gets emptied by
repository scanner
SQL Server database gets emptied by repository scanner
------------------------------------------------------
Key: MRM-1078
URL: http://jira.codehaus.org/browse/MRM-1078
Project: Archiva
Issue Type: Bug
Components: repository scanning
Affects Versions: 1.2-M1, 1.1.3, 1.1.2, 1.1.1
Environment: Windows XP SP3; Java Sun JDK 1.6.0_11; SQL Server 2005; Archiva running in JBoss 5.0.0.GA
Reporter: Bob Walker
Attachments: repscan.csv
When Using SQL Server as a backing store, the repository scanner regularly empties my database, specifically the ARCHIVA_ARTIFACT table, despite the files still existing on disk. This does NOT happen when using Derby as the backing store.
Strangely, and possibly significantly, the only artifacts left in that table after a scan are the JUnit jar and POM that is recommended as a post-install test in the documentation.
All the other files in the Maven repo were copied from another server installation. I have seen the other JIRA issues relating to timestamps, but I don't think this is the issue.
As a test, I have truncated the ARCHIVA_REPOSITORY_STATS table, then re-scanned - this does re-populate the ARCHIVA_ARTIFACT table with the 9000+ files I have in my repo, but only temporarily, subsequent scans empty the table.
The files on disk are not changing, with the exception of a handful of artifacts that I deploy to the repo periodically via Hudson builds.
I've attached the last contents of my ARCHIVA_REPOSITORY_STATS table before I switched back to Derby, which works (all files remain visible in Archiva).
--
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
[jira] Closed: (MRM-1078) SQL Server database gets emptied by
repository scanner
Posted by "Bob Walker (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Walker closed MRM-1078.
---------------------------
Resolution: Not A Bug
My mistake, sorry. I had another test installation on another server pointing at the same database.
> SQL Server database gets emptied by repository scanner
> ------------------------------------------------------
>
> Key: MRM-1078
> URL: http://jira.codehaus.org/browse/MRM-1078
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 1.1.1, 1.1.2, 1.1.3, 1.2-M1
> Environment: Windows XP SP3; Java Sun JDK 1.6.0_11; SQL Server 2005; Archiva running in JBoss 5.0.0.GA
> Reporter: Bob Walker
> Attachments: repscan.csv
>
>
> When Using SQL Server as a backing store, the repository scanner regularly empties my database, specifically the ARCHIVA_ARTIFACT table, despite the files still existing on disk. This does NOT happen when using Derby as the backing store.
> Strangely, and possibly significantly, the only artifacts left in that table after a scan are the JUnit jar and POM that is recommended as a post-install test in the documentation.
> All the other files in the Maven repo were copied from another server installation. I have seen the other JIRA issues relating to timestamps, but I don't think this is the issue.
> As a test, I have truncated the ARCHIVA_REPOSITORY_STATS table, then re-scanned - this does re-populate the ARCHIVA_ARTIFACT table with the 9000+ files I have in my repo, but only temporarily, subsequent scans empty the table.
> The files on disk are not changing, with the exception of a handful of artifacts that I deploy to the repo periodically via Hudson builds.
> I've attached the last contents of my ARCHIVA_REPOSITORY_STATS table before I switched back to Derby, which works (all files remain visible in Archiva).
--
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