Details
-
Bug
-
Resolution: Handled by Support
-
Highest
-
None
-
2.6.1
-
None
-
RHEL 5.5
MySQL DB
Description
This error is ocuring in all our CVS repositories:
2011-07-03 04:41:34,584 ERROR [IncrementalPinger1 ] fisheye.app com.cenqua.fisheye.cvsrep.cache.CvsHistoryChangeDetector-doRunOnce - problem with initial scan
com.cenqua.fisheye.rep.DbException: Error during upgrade task upgrade-changeset-ancestry-3 on <cvs_repository_name>
at com.cenqua.fisheye.rep.impl.BaseUpgradeTask.upgrade(BaseUpgradeTask.java:67)
at com.cenqua.fisheye.cvsrep.cache.CachedCvsRepositoryUpdater.upgrade(CachedCvsRepositoryUpdater.java:293)
at com.cenqua.fisheye.cvsrep.cache.CvsHistoryChangeDetector.doRunOnce(CvsHistoryChangeDetector.java:117)
at com.cenqua.fisheye.cvsrep.cache.CvsHistoryChangeDetector.ping(CvsHistoryChangeDetector.java:54)
at com.cenqua.fisheye.cvsrep.cache.CachedCvsRepositoryUpdater.pingSlurp(CachedCvsRepositoryUpdater.java:279)
at com.cenqua.fisheye.cvsrep.CvsRepositoryEngine.doSlurp(CvsRepositoryEngine.java:68)
at com.cenqua.fisheye.rep.RepositoryEngine.slurp(RepositoryEngine.java:390)
at com.cenqua.fisheye.rep.ping.OneOffPingRequest.doRequest(OneOffPingRequest.java:25)
at com.cenqua.fisheye.rep.ping.PingRequest.process(PingRequest.java:66)
at com.cenqua.fisheye.rep.RepositoryHandle.processPingRequests(RepositoryHandle.java:132)
at com.cenqua.fisheye.rep.RepositoryHandle.queuePingRequest(RepositoryHandle.java:122)
at com.cenqua.fisheye.rep.ping.PingRequest.run(PingRequest.java:33)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Ater that it continuously throws the following warning:
2011-07-06 15:49:10,112 WARN [IncrementalPinger1 ] fisheye.app com.cenqua.fisheye.rep.impl.TopologicalOrderChangesetIterator-addCsAndParentsToFront - TopologicalOrderChangesetIterator.addCsAndParentsToFront: Cyclic Ancestry Detected: [<branch>:<commiter>:20010906035716(<branch>:<commiter>:20010905030326,), ][<branch>:<commiter>:20010821002214(<branch>:<commiter>:20010906035716,), <branch>:<commiter>:20010905030326(<branch>:<commiter>:20010821002214,), <branch>:<commiter>:20010908015841(<branch>:<commiter>:20010906035716,), <branch>:<commiter>:20010717175148(<branch>:<commiter>:20010908015841,), ]
It then causes the application to hang. And in the admin's repository view, the currently being scanned repositories have the following:
Info
Upgrading Ancestry for ChangeSet: <branch>:<commiter>:20010906035716 (x of n)
Although we can trigger individual repository indexing manually, this bug prevents automatic indexing to occur and takes up all of the CPU core (and then some) it's running on.
This seems to be a show stopper for our very active instance of Fisheye/Crucible and prevents any reviews/work to be done in coordination with this product.
If there is anything I can provide to help fix this bug, please say so.
