Fisheye throws "Exception getting annotation" when indexing a Perforce repository
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
Problem
Fisheye does not complete the indexing of a Perforce repository, and the content of the files is not searchable in Fisheye.
When performing the following action:
retrieving the annotations for a file
The following appears in the atlassian-fisheye-YYYY-MM-DD.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
WARN [IncrPing1 repository_name ] fisheye RepositoryConfig-isOfIndexableSize - [repository_name] pathtofile/filename exceeds indexing size limit (10M, limit is 5M). The contents of this file won't be searchable in FishEye.
ERROR [IncrPing1 repository_name ] fisheye P4Cache-getBlameFallback - Exception getting annotation for pathtofile/filename@revision
com.cenqua.fisheye.perforce.client.P4ClientException: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | File size exceeds dm.annotate.maxsize (10485760 bytes).
at com.cenqua.fisheye.perforce.client.P4Client.getBlame(P4Client.java:510) [fisheye.jar:?]
at com.cenqua.fisheye.perforce.P4Cache.getBlameFallback(P4Cache.java:366) [fisheye.jar:?]
at com.cenqua.fisheye.rep.BaseBlameAndLinecountCalculator.calcBlameFromScm(BaseBlameAndLinecountCalculator.java:392) [fisheye.jar:?]
...
WARN [IncrPing1 repository_name ] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo repository_name due to class com.cenqua.fisheye.rep.DbException - java.io.IOException: Exception getting annotation blame: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | File size exceeds dm.annotate.maxsize (10485760 bytes).
com.cenqua.fisheye.rep.DbException: java.io.IOException: Exception getting annotation blame: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | File size exceeds dm.annotate.maxsize (10485760 bytes).
at com.cenqua.fisheye.rep.BaseBlameAndLinecountCalculator.calcBlameFromScm(BaseBlameAndLinecountCalculator.java:445) [fisheye.jar:?]
at com.cenqua.fisheye.rep.BaseBlameAndLinecountCalculator.calcBlame(BaseBlameAndLinecountCalculator.java:281) [fisheye.jar:?]
at com.cenqua.fisheye.rep.BaseBlameAndLinecountCalculator.calculateRevisionData(BaseBlameAndLinecountCalculator.java:177) [fisheye.jar:?]
...
Caused by: java.io.IOException: Exception getting annotation blame: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | File size exceeds dm.annotate.maxsize (10485760 bytes).
at com.cenqua.fisheye.perforce.P4Cache.getBlameFallback(P4Cache.java:370) [fisheye.jar:?]
at com.cenqua.fisheye.rep.BaseBlameAndLinecountCalculator.calcBlameFromScm(BaseBlameAndLinecountCalculator.java:392) [fisheye.jar:?]Cause
The Perforce p4 annotate command fails due to a file exceeding the dm.annotate.size setting.
Resolution
Set or Increase the value of the
dm.annotate.maxsizeto be higher than the limit reported in the log file. More information regarding this setting are available on the Perforce annotate page.
Was this helpful?