Fisheye Repository Scan Aborts with 'Timer already cancelled' Exception
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When scanning a repository, the following error is reported:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
ERROR - exception in change detector
com.cenqua.fisheye.config.ConfigException: Could not access file:///dm2/repos/DMS/ : Timer already cancelled.
at com.cenqua.fisheye.svn.SvnRepositoryTester.pingAndValidateAccess(Crucible-1.1.3-build-247:112)
at com.cenqua.fisheye.svn.SvnRepositoryScanner.validateAccess(Crucible-1.1.3-build-247:223)
at com.cenqua.fisheye.rep.RepositoryScanner.slurpRepository(Crucible-1.1.3-build-247:343)
.....
.....
Caused by: java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Unknown Source)
at java.util.Timer.schedule(Unknown Source)
at com.cenqua.fisheye.svn.SvnThrottledClient.start(Crucible-1.1.3-build-247:50)
.....
.....
... 10 more
Cause
This can occur when not enough memory is allocated to Fisheye.
Resolution
To solve this error, you will need to increase memory allocated to Fisheye.
After having set the FISHEYE_OPTS and restarting your server, go to Administration > Sys Info/Support > System Info, and check your JVM Input Arguments to ensure that your server is picking up your FISHEYE_OPTS as expected.
Was this helpful?