[MRM-1095] Archiva keeps scanning repositories, even if scanning disabled in the web UI

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2-M1
• Fix Version/s: 1.2
• Component/s: repository scanning
• Assignee: james.w.dumay
• Reporter: Gwen Harold Autencio
• Created: 22/Feb/09 23:37
• Updated: 21/Mar/09 21:01
• Resolved: 05/Mar/09 22:30

Description

Archiva logs show:

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

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