Troubleshooting

Crucible Troubleshooting

The most common cause of Fisheye/Crucible issues is an incorrect symbolic setup (trunk/branch/tag) for Subversion repositories. If you are using Subversion and your initial index is taking forever, double-check that your symbolic setup matches your repository.

Fisheye runs with the default Java heap of 64 megabytes. This is sometimes problematic for Fisheye, especially for Subversion repositories during the initial scan. You can give Fisheye's JVM more memory by setting the FISHEYE_OPTS environment variable.

Starting Crucible with the command line options --debug --debug-perf will print a lot of information to Crucible's logs. This can give you an insight into what is happening and possibly where you are stuck. Attach these logs along with your config.xml to an Atlassian support ticket, to speed up your support request.