JIRA startup failed due to spring context error.

[Shun Hirayanagi]

I have a JIRA standalone instance whose version is 5.1.8.

JIRA startup occasionally fails, not always. atlassian-jira.log gives the following message.

2013-07-24 04:36:04,492 Spring executor 6 ERROR [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] Expecting state (resolving-dependencies) not (dependencies-resolved) for context [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.dashboard, config=osgibundle:/META-INF/spring/*.xml)]; assuming an interruption and bailing out

Do you have any ideas why this happens?

I searched related questions and found some examples.

https://answers.atlassian.com/questions/28331/confluence-system-plugins-failing-on-startup

https://answers.atlassian.com/questions/31411/error-setting-up-jira

But these cases seem to be due to time out. My atlassian-jira.log doesn't contain the phrase "time out", so I don't think these cases and my case have the same cause.

[Shun Hirayanagi · Accepted solution]

I found that an anti-virus software which I used caused this problem. I made the anti-virus software exclude ${JIRA.HOME}/data/plugins/.osgi-plugins from real-time scanning.
This problem have never happened since that.

[Radu Dumitriu]

http://static.springsource.org/spring-osgi/snapshot-site/spring-osgi-extender/xref/org/springframework/osgi/extender/internal/dependencies/startup/DependencyWaiterApplicationContextExecutor.html

What causes it is that the stageTwo() is probably called the second time (spring bug ?). However, this needs more info, and more debug than the simple text here ....

[Shun Hirayanagi]

Thanks.

What can I do to get more info?

[C_ Faysal]

hi.

i'd suggest this one

https://answers.atlassian.com/questions/187616/few-exceptions-while-bringing-up-jira-5-2-10

seems to be an indexing (cache) problem on your side.

[Shun Hirayanagi]

Thank you for your comment.

Although the first messages of two log files are the same, there is no message like "caches/indexes does not exist" in my log file. So, I think my index files have no problem.