Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Fisheye upgrade (Error parsing config.xml) error

Hi All,


I am trying to upgrade fisheye from 2.9.1 to 3.5.4, I did all the config changes and copied the config.xml file from old fisheye to new one, changing the DB parameters accordingly (created seperate db for new fisheye instance). I am now getting below error in logs while trying to start new fisheye instance:


2014-11-17 06:14:03,396 INFO - loading config from file: /app/share/fisheye/fecru-3.5.4-home/config.xml
2014-11-17 06:14:03,776 ERROR - Errors parsing /app/share/fisheye/fecru-3.5.4-home/config.xml:
2014-11-17 06:14:03,777 ERROR - at line 226: Element 'config@' with element-only content type cannot have text content.
2014-11-17 06:14:03,778 ERROR - Problem with config file: Error parsing config file (see logs): /app/share/fisheye/fecru-3.5.4-home/config.xml
com.cenqua.fisheye.config.ConfigException: Error parsing config file (see logs): /app/share/fisheye/fecru-3.5.4-home/config.xml
at com.cenqua.fisheye.config.RootConfig.load(
at com.cenqua.fisheye.ctl.Run.mainImpl(
at com.cenqua.fisheye.ctl.Run.main(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at com.cenqua.fisheye.FishEyeCtl.mainImpl(
at com.cenqua.fisheye.FishEyeCtl.main(

Could you please assist me with this?

Thanks and Regards,


3 answers

1 accepted

0 votes
Answer accepted

This issue is resolved now. There is a difference in the database parameters in fisheye 2.9.1 and 3.5.4. I retained the fisheye 3.5.4 db parameters format and manually copied the configuration from fisheye 2.9.1 to 3.5.4  into config.xml file. That resolved the issue for me.


Thanks all!


Jenin Mohan

1 vote

Hi Jenin,

Can you please take a look at and check if its resolution is helpful? The error message present in this document is similar to yours.

In case it doesn't help, please also give a try validating your XML as insructed at Check for any misspelling you could have inserted in case you changed the config.xml manually.


Gustavo Refosco

Hi Gustavo, I have validated my xml and it does not found any errors in it. Further, the error on the above link is a bit different. Any suggestion? Regards, Jenin Mohan

0 votes
lpater Atlassian Team Nov 17, 2014

Hi Jenin,

the error seems to be caused by your <config> element in the config.xml having text content, where it's only expected to contain other elements.

Something like this would trigger the error:

&lt;config version="1.0" control-bind=""&gt;

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events