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@http://www.cenqua.com/fisheye/config-1' 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Could you please assist me with this?
Thanks and Regards,
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.
Can you please take a look at https://confluence.atlassian.com/display/FISHKB/FishEye+fails+to+start+up+with+parsing+error+in+config.xml 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 https://confluence.atlassian.com/pages/viewpage.action?pageId=633439765. Check for any misspelling you could have inserted in case you changed the config.xml manually.
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:
<config version="1.0" control-bind="127.0.0.1:6061"> NO-TEXT-EXPECTED-HERE <web-server> ... </config>
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot