"Updates" column for SVN repositories stuck in "Scanning 100%"

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 4.9.1
    • Affects Version/s: 4.9.0
    • Component/s: User interface
    • None
    • Minor
    • 2

      Issue Summary

      This issue is reproducible on Fisheye/Crucible 4.9.0: yes

      Steps to Reproduce

      1. Add SVN repositories to Fisheye/Crucible 4.9.0.
      2. Go to Cog icon > Repositories.
      3. Notice that even after the SVN repository is indexed successfully, the "Updates" column is stuck showing "Scanning 100%".

      Expected Results

      The "Updates" column should show the index as completed and display the last updated time.

      Actual Results

      Even after the SVN repository is indexed successfully, the "Updates" column remains stuck showing "Scanning 100%".

      In the logs, we can see the InitPing threads during the indexing process:

      2025-02-18 16:59:41,308 INFO  [InitPing3 LargeBinRepo ] com.cenqua.fisheye.rep.BaseRepositoryScanner - done slurp for repository LargeBinRepo (LargeBinRepo) time = 60 ms
2025-02-18 16:59:41,309 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.rep.RepositoryStatus - Status change [LargeBinRepo]: Indexing all review data.
2025-02-18 16:59:41,309 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.util.Timer - -> Review fullscan for LargeBinRepo mem_usage = 406791328 heapsize = 812646400 freemem = 405855072
2025-02-18 16:59:41,310 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.rep.impl.ReviewInfoDAO - deleted 0 old index messages
2025-02-18 16:59:41,311 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.rep.impl.ReviewInfoDAO - indexed 0 Crucible rows.
2025-02-18 16:59:41,311 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.util.Timer - <- Review fullscan for LargeBinRepo  time 2 millis mem_usage = 408189800 heapsize = 812646400 freemem = 404456600
2025-02-18 16:59:41,318 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.cache.BaseRevisionCache - Task ReviewInfoDAO#slurp committed for priority 30 total= 10 ms (lock= 0 ms, task=3 ms, commit=7 ms)
2025-02-18 16:59:41,323 DEBUG [InitPing3 LargeBinRepo ] com.cenqua.fisheye.rep.RepositoryHandle - release engine on LargeBinRepo, count=0 waited 0 ms to release
2025-02-18 16:59:41,323 DEBUG [InitPing3 ] com.cenqua.fisheye.rep.RepositoryHandle - acquire engine on LargeBinRepo, count=1, waited 0 ms to acquire.
2025-02-18 16:59:41,323 DEBUG [InitPing3 ] com.cenqua.fisheye.rep.RepositoryHandle - release engine on LargeBinRepo, count=0 waited 0 ms to release

      And we can see the IncrPing threads during the polling as well:

      2025-02-18 17:26:41,257 INFO  [IncrPing2 LargeBinRepo ] com.cenqua.fisheye.rep.BaseRepositoryScanner - processing repository LargeBinRepo (LargeBinRepo)
2025-02-18 17:26:41,257 INFO  [IncrPing2 LargeBinRepo ] com.atlassian.fisheye.svn.Svn2Scanner - Starting slurp of LargeBinRepo (LargeBinRepo)
2025-02-18 17:26:41,257 DEBUG [SvnExecution15 LargeBinRepo ] com.cenqua.fisheye.svn.SvnTask - Executing (IncrPing2 LargeBinRepo) svn info -r HEAD http://10.224.214.96/svn/LargeBinRepo/@HEAD
2025-02-18 17:26:41,263 DEBUG [IncrPing2 LargeBinRepo ] com.cenqua.fisheye.rep.RepositoryStatus - Status change [LargeBinRepo]: Obtaining changeset list
2025-02-18 17:26:41,263 DEBUG [IncrPing2 LargeBinRepo ] com.atlassian.fisheye.svn.Svn2WrapUpProcessor - Started wrapup processing: startRevision=14, lastScannedCsid=13
2025-02-18 17:26:41,263 DEBUG [IncrPing2 LargeBinRepo ] com.atlassian.fisheye.svn.Svn2WrapUpProcessor - Completed wrapup processing: lastCsProcessed=-1
2025-02-18 17:26:41,263 INFO  [IncrPing2 LargeBinRepo ] com.cenqua.fisheye.rep.BaseRepositoryScanner - done slurp for repository LargeBinRepo (LargeBinRepo) time = 6 ms
2025-02-18 17:26:41,263 DEBUG [IncrPing2 LargeBinRepo ] com.cenqua.fisheye.rep.RepositoryHandle - release engine on LargeBinRepo, count=0 waited 0 ms to release
2025-02-18 17:26:41,263 DEBUG [IncrPing2 ] com.cenqua.fisheye.rep.RepositoryHandle - acquire engine on LargeBinRepo, count=1, waited 0 ms to acquire.
2025-02-18 17:26:41,263 DEBUG [IncrPing2 ] com.cenqua.fisheye.rep.RepositoryHandle - release engine on LargeBinRepo, count=0 waited 0 ms to release

      Although the threads report successful indexing, the UI continues to display "Scanning 100%" as if stuck and not receiving responses from the backend.

      Workaround

      This is only a UI bug. The actual repository, commits, and other features are working as expected, even though the "Updates" column shows "Scanning 100%".

            Assignee:
            Unassigned
            Reporter:
            Gustavo Saviano Silva (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: