Fisheye fails to start up with parsing error in config.xml

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

Fisheye fails to startup with following error reported in the fisheye-debug-<date>.log:

1 2 3 4 5 6 2012-12-05 18:50:00,431 ERROR - Errors parsing /Path/to/config.xml: 2012-12-05 18:50:00,431 ERROR - at line <Line No.>: Expected attribute: rep in element map@<Some URL> 2012-12-05 18:50:00,432 ERROR - Problem with config file: Error parsing config file (see logs): /Path/to/config.xml

atlassian-fisheye-<date>.log:

1 2 3 4 5 6 7 2013-11-20 09:27:11,597 ERROR [main ] fisheye.app RootConfig-load - Errors parsing C:\Atlassian\fisheyedata\config.xml: 2013-11-20 09:27:11,598 ERROR [main ] fisheye.app RootConfig-logXmlErrors - at line 225: Expected element 'api@http://www.cenqua.com/fisheye/config-1' instead of 'smtp@http://www.cenqua.com/fisheye/config-1' here in element config@http://www.cenqua.com/fisheye/config-1 2013-11-20 09:27:11,616 ERROR [main ] fisheye.app Run-mainImpl - Problem with config file: Error parsing config file (see logs): C:\Atlassian\fisheye-crucible-data\config.xml 2013-11-20 09:27:11,617 INFO [main ] fisheye.app Run-mainImpl - CE com.cenqua.fisheye.config.ConfigException: Error parsing config file (see logs): C:\Atlassian\fisheyedata\config.xml at com.cenqua.fisheye.config.RootConfig.load(RootConfig.java:148) at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:112)

Cause

  1. This feature is being used in Fisheye.

    For some reason, the rep element is missing in the <FISHEYE_INST>/config.xml file here:

    1 <viewcvs-url-mapper><map viewcvsname="<Some URL>"/></viewcvs-url-mapper>

    As you can see from the link above, the ViewCVS name needs an associated repository with it, which is missing from the above tag.

    OR

  2. Older version of Fisheye/Crucible is started.

Resolution

  1. Update this element:

    1 <viewcvs-url-mapper><map viewcvsname="<Some URL>"/></viewcvs-url-mapper>

    as follows:

    1 <viewcvs-url-mapper><map viewcvsname="<Some URL>" rep="<Repository Name>"/></viewcvs-url-mapper>

    Note the "rep" tag after the "viewcvsname" tag. Add your repository name to this tag.

    Restart your Fisheye instance after modifying the <FISHEYE_HOME>/config.xml file.

  2. Make sure that you are starting the latest version of Fisheye/Crucible in your server.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.