Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Unable to start fisheye verison 2.5.1

Dhananjay Mukhedkar August 13, 2014

Hi Team,

I am trying to start fisheye. However, I am getting the following error,

Problem connecting to null
org.apache.xmlbeans.XmlException: error: Unexpected end of file after null
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3471)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1270)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1257)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
at com.cenqua.fisheye.config1.ConfigDocument$Factory.parse(ConfigDocument.java:801)
at com.cenqua.fisheye.config.RootConfig.parseDocument(RootConfig.java:189)
at com.cenqua.fisheye.config.RootConfig.parseDocument(RootConfig.java:179)
at com.cenqua.fisheye.ctl.BaseRemoteCommand.mainImpl(BaseRemoteCommand.java:52)
at com.cenqua.fisheye.ctl.Stop.main(Stop.java:11)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:113)
at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)
Caused by: org.xml.sax.SAXParseException: Unexpected end of file after null
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)

Please let me know the fix on this issue.

Regards

Dhananjay

1 answer

0 votes
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 13, 2014

Hi Dhananjay

it looks as if your config.xml file is corrupted, and FishEye can't read it. Please have a look at the file and see if it looks valid and is not truncated. Try restoring it from a backup if so.

Dhananjay Mukhedkar August 13, 2014

Hi Lukasz,

Thanks for your reply. Please let me know how we can check whether the file named config.xml file is corrupted.

Regards

Dhananjay

lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 13, 2014

The fastest way would probably to raise a support ticket at http://support.atlassian.com/and attach your config.xml

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events