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
4,256,849
Community Members
 
Community Events
164
Community Groups

Can't restart Fisheye

We had a problem in Jira, which was restarted and seems OK now, except that it can't contact Fisheye. Checked Fisheye, which used 100% CPU, so I stopped it and then restarted, but it wouldn't restart.

Error log says Problem starting repository repeatedly and ends with an ERROR, see below.

I will include the entire error log in a minute.

Is there an easy way to stop Jira from trying to connect to Fisheye? Disable the plugin(s)? It is filling up the log, one line per second.

Fisheye error log tail:

...

2011-12-14 14:51:57,915 WARN main fisheye.app com.cenqua.fisheye.config.DefaultRepositoryManager-runRepositories - Problem starting repository

java.lang.RuntimeException: Application Context not initialised.

at com.cenqua.fisheye.config.SpringContext.getApplicationContext(SpringContext.java:34)

at com.cenqua.fisheye.config.SpringContext.getComponentByClass(SpringContext.java:73)

at com.cenqua.fisheye.rep.RepositoryHandle.getIndexingContext(RepositoryHandle.java:570)

at com.cenqua.fisheye.rep.RepositoryHandle.run(RepositoryHandle.java:303)

at com.cenqua.fisheye.config.DefaultRepositoryManager.runRepository(DefaultRepositoryManager.java:259)

at com.cenqua.fisheye.config.DefaultRepositoryManager.runRepositories(DefaultRepositoryManager.java:287)

at com.cenqua.fisheye.config.RootConfig.startRepositories(RootConfig.java:521)

at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:248)

at com.cenqua.fisheye.ctl.Run.main(Run.java:69)

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:592)

at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:113)

at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)

2011-12-14 14:51:57,917 WARN main fisheye.app com.cenqua.fisheye.config.DefaultRepositoryManager-runRepositories - Problem starting repository

java.lang.RuntimeException: Application Context not initialised.

at com.cenqua.fisheye.config.SpringContext.getApplicationContext(SpringContext.java:34)

at com.cenqua.fisheye.config.SpringContext.getComponentByClass(SpringContext.java:73)

at com.cenqua.fisheye.rep.RepositoryHandle.getIndexingContext(RepositoryHandle.java:570)

at com.cenqua.fisheye.rep.RepositoryHandle.run(RepositoryHandle.java:303)

at com.cenqua.fisheye.config.DefaultRepositoryManager.runRepository(DefaultRepositoryManager.java:259)

at com.cenqua.fisheye.config.DefaultRepositoryManager.runRepositories(DefaultRepositoryManager.java:287)

at com.cenqua.fisheye.config.RootConfig.startRepositories(RootConfig.java:521)

at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:248)

at com.cenqua.fisheye.ctl.Run.main(Run.java:69)

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:592)

at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:113)

at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)

2011-12-14 14:51:57,917 ERROR main fisheye.app com.cenqua.fisheye.ctl.Run-mainImpl - Could not start quartz schedule: Application Context not in itialised.

java.lang.RuntimeException: Application Context not initialised.

at com.cenqua.fisheye.config.SpringContext.getApplicationContext(SpringContext.java:34)

at com.cenqua.fisheye.config.SpringContext.getComponent(SpringContext.java:65)

at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:252)

at com.cenqua.fisheye.ctl.Run.main(Run.java:69)

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:592)

at com.cenqua.fisheye.FishEyeCtl.mainImpl(FishEyeCtl.java:113)

at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)

5 answers

1 accepted

0 votes
Answer accepted

This is the same as FSH-7549, which is solved and closed.

Had to run mysqladmin flush-servers because the mysql server was blocked due to earlier network problems.

And yes, citnet admin, you were right, fisheye had started but not completely, couldn't contact the database. Jira couldn't contact Fisheye. After the flush-seervers command everything was OK.

Can any body help , i am also facing the same issue.I cant start my fisheye instance.

Fishseye 2.7

Postgres database

error message is :

ERROR: problem running command
java.lang.reflect.InvocationTargetException
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:98)
at com.cenqua.fisheye.FishEyeCtl.main(FishEyeCtl.java:41)
Caused by: java.lang.ArrayIndexOutOfBoundsException: -1
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.isASCIINameCharNS(PiccoloLexer.java:2483)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseAttributeNameNS(PiccoloLexer.java:2042)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseAttributesNS(PiccoloLexer.java:1713)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseOpenTagNS(PiccoloLexer.java:1521)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseTagNS(PiccoloLexer.java:1362)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXMLNS(PiccoloLexer.java:1293)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXML(PiccoloLexer.java:1261)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:4808)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3439)
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:876)
at com.cenqua.fisheye.config.RootConfig.parseDocument(RootConfig.java:181)
at com.cenqua.fisheye.config.RootConfig.parseDocument(RootConfig.java:171)
at com.cenqua.fisheye.config.RootConfig.load(RootConfig.java:144)
at com.cenqua.fisheye.ctl.Run.mainImpl(Run.java:113)
at com.cenqua.fisheye.ctl.Run.main(Run.java:77)
... 6 more

I am also having same problem with my fisheye. After it tooks 100% of the directory in the server, I deleted the fisheye.lck file and now it is giving me the exact same error. How to resolve this issue?

im getting the same error in fisheye 2.7, connect to mssql server 2008, can some one plz support

even the log messages are same as mentioned in this case

Are you sure the fisheye process has been stopped? Check your running processes.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

#JiraHeroes May '22 Spotlight: Daniel Cave

At Atlassian, we take great pride in the software we ship, and even greater pride in the success our customers achieve when they use our products. #JiraHeroes is our new monthly spotlight series&nbsp...

856 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you