Downloads (PDF, HTML & XML formats)
[FishEye Knowledge Base]
This page lists the Java VM system properties which may be set to control certain aspects of FishEye and Crucible's behaviour. Please refer to Setting JVM System Properties for how to set these properties in your instance. The version column indicates the version of FishEye/Crucible from which the property is applicable.
| Property Name | Values | Default | Purpose | Version |
|---|---|---|---|---|
fisheye.branch.recently.active.check.limit | number of branches | 250 | Used in CommitGraph to control sorting of branches. If more than the limit, sorted alphabetically, otherwise sorted by recent activity. | 2.6.0 |
fisheye.git.http-backend-timeout | Integer milliseconds | 3600000 | This property sets the amount of time that the FishEye server should allow the underlying Git process to execute when attempting to serve a Git push or pull request. | 2.7.3 |
fisheye.p4.disable.ancestry | true/false | false | If true, stops FishEye from processing P4 ancestry information. If you do not use stable Perforce branchspecs to manage branches, set this to true. | 2.7.5 |
fisheye.search.max.repositories | number of repositories | 100 | Used by FishEye to limit the search to the top n repositories (by alphabetical order) when a cross-repository search is performed. | 2.7.12 |
crucible.detect.metadata.revision.changes | true/false | true | If true, detects and disables creation of reviews from changesets which contain metadata only changes (e.g svn property changes). Read more here. | 2.6.0 |
jetty.http.headerbuffersize | bytes | 4096 | This controls the size of the largest HTTP header value that FishEye will allow (through its embedded servlet engine, Jetty). Some authentication systems require larger header values. | 1.6.5 |
org.eclipse.jetty.server.Request.maxFormContentSize | bytes | 3000000 | Max form content size – increase this value if your Git push fails with HTTP error 411 (see this KB article: Git PUSH results in RPC failed, result=22, HTTP code = 413) | 3.0.0 |
fisheye.changeset.paths.limit | number of paths | 10000 | This setting is to prevent extremely large changesets (which are often the result of an error) from slowing FishEye/Crucible down. See Indexed paths truncated at 10000 for the messages that are logged if the value is reached. | |
crucible.review.content.size.limit | number of file revisions allowed in a review | 800 | Limits the "size" of a review to prevent extremely large reviews accidentally being created and potentially slowing the instance down. | 2.10.0 |
| System Property | Legal values | Default Value | Description | FishEye version |
|---|---|---|---|---|
fisheye.pipeline.threads | 4 - 1000 | The number of processor cores detected, or 4, whichever is greater | The number of threads available to work on indexing tasks. A higher value allows for potentially greater concurrency in indexing activities, but will increase the load on the server and the load on your SCM. | 3.0.0 |
fisheye.pipeline.fairness | true, false | true | If If | 3.0.0 |
fisheye.pipeline.batch.cslimit | 1 - 50000 | 10000 | The pipeline processes changesets in batches. A bigger batch size reduces the number of calls to the underlying SCM, but also increases heap consumption and reduces the concurrency of the pipeline. Smaller batch sizes increase the concurrency of the pipeline, reduce heap consumption, but result in more calls to the underlying SCM. | 3.0.0 |
fisheye.pipeline.batch.pathlimit | 1000 - 120000 | 60000 | The pipeline processes changesets in batches. This property sets the maximum allowed number of unique paths in a batch (summed across changesets). A higher value will reduce the number of calls to the underlying SCM, at the expense of more heap consumption. | 3.0.0 |
Related Topics
Overview
Content Tools
Apps
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.