You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Gwen Harold Autencio (JIRA)" <ji...@codehaus.org> on 2009/02/23 06:38:19 UTC

[jira] Created: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Archiva keeps scanning repositories, even if scanning disabled in the web UI
----------------------------------------------------------------------------

                 Key: MRM-1095
                 URL: http://jira.codehaus.org/browse/MRM-1095
             Project: Archiva
          Issue Type: Bug
          Components: repository scanning
            Reporter: Gwen Harold Autencio


Archiva logs show: 

{noformat}
2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
.\ Scan of internal \.__________________________________________
  Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
  Repository Name   : Archiva Managed Internal Repository
  Repository Layout : default
  Known Consumers   : (6 configured)
                      metadata-updater
                      auto-remove
                      auto-rename
                      update-db-artifact
                      create-missing-checksums
                      index-content
  Invalid Consumers : <none>
  Duration          : 173 Milliseconds
  When Gathered     : 2/23/09 12:15 PM
  Total File Count  : 7
  Avg Time Per File : 24 Milliseconds
{noformat} 

Even though scanning is disabled for that particular repository in the web UI.
Even after Archiva restart, the problem persists.

-- 
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] Updated: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1095:
----------------------------------

    Fix Version/s:     (was: 1.2-M2)
                   1.2

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Commented: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166812#action_166812 ] 

James William Dumay commented on MRM-1095:
------------------------------------------

Committed patch in -r747198.

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2-M2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Assigned: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James William Dumay reassigned MRM-1095:
----------------------------------------

    Assignee: James William Dumay

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Work started: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MRM-1095 started by James William Dumay.

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2-M2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James William Dumay closed MRM-1095.
------------------------------------

    Resolution: Fixed

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2-M2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Updated: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James William Dumay updated MRM-1095:
-------------------------------------

    Affects Version/s: 1.2-M1
        Fix Version/s: 1.2-M2

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2-M2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Updated: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "Gwen Harold Autencio (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gwen Harold Autencio updated MRM-1095:
--------------------------------------

    Attachment: MRM-1095.patch

Hi attached patch, for fix of the issue.
Checks if isScanned value a ManagedRepositoryConfiguration before being scheduled to be scanned.

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>            Reporter: Gwen Harold Autencio
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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] Commented: (MRM-1095) Archiva keeps scanning repositories, even if scanning disabled in the web UI

Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166810#action_166810 ] 

James William Dumay commented on MRM-1095:
------------------------------------------

Thanks Gwen! Are we able to get a unit test for this too please?

> Archiva keeps scanning repositories, even if scanning disabled in the web UI
> ----------------------------------------------------------------------------
>
>                 Key: MRM-1095
>                 URL: http://jira.codehaus.org/browse/MRM-1095
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.2-M1
>            Reporter: Gwen Harold Autencio
>            Assignee: James William Dumay
>             Fix For: 1.2-M2
>
>         Attachments: MRM-1095.patch
>
>
> Archiva logs show: 
> {noformat}
> 2009-02-23 12:15:01,837 [pool-2-thread-1] INFO  org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor  - Finished repository task: 
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /home/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/appserver-base/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (6 configured)
>                       metadata-updater
>                       auto-remove
>                       auto-rename
>                       update-db-artifact
>                       create-missing-checksums
>                       index-content
>   Invalid Consumers : <none>
>   Duration          : 173 Milliseconds
>   When Gathered     : 2/23/09 12:15 PM
>   Total File Count  : 7
>   Avg Time Per File : 24 Milliseconds
> {noformat} 
> Even though scanning is disabled for that particular repository in the web UI.
> Even after Archiva restart, the problem persists.

-- 
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