Jira deployment dependency errors

Jason Varsoke March 10, 2012

Trying to install my first Jira-5.0 on Debian Linux with Tomcat6. The following is the start of a dependency error stream in catalina.out. Any suggestions on what's missing and how to fix it?

2012-03-10 18:31:32,638 main INFO      [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/home/plugins/.bundled-plugins/workflow-designer-plugin-2.5.2.jar (1329344548000) created
2012-03-10 18:34:29,450 Timer-0 WARN      [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.activeobjects.activeobjects-plugin, config=osgibundle:/META-INF/spring/*.xml)]
2012-03-10 18:34:29,766 Timer-0 ERROR      [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.activeobjects.activeobjects-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.sal.api.pluginsettings.PluginSettingsFactory)] (from bean [&pluginSettingsFactory]), Dependency on [(objectClass=com.atlassian.sal.api.user.UserManager)] (from bean [&userManager]), Dependency on [(objectClass=com.atlassian.sal.api.auth.LoginUriProvider)] (from bean [&loginUriProvider]), Dependency on [(objectClass=com.atlassian.sal.api.websudo.WebSudoManager)] (from bean [&webSudoManager]), Dependency on [(objectClass=com.atlassian.sal.api.message.I18nResolver)] (from bean [&i18nResolver]), Dependency on [(objectClass=com.atlassian.sal.api.message.HelpPathResolver)] (from bean [&helpPathResolver])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.activeobjects.activeobjects-plugin' has timed out
        at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454)
        at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50)
        at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105)
        at java.util.TimerThread.mainLoop(Timer.java:534)
        at java.util.TimerThread.run(Timer.java:484)
...

2 answers

0 votes
Andrew Frayling
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 15, 2012

Hi,

Not that nobody cares, probably more that people haven't come across this error before. There was a similar problem posted at https://answers.atlassian.com/questions/18327/unzipped-jira-stand-alone-initial-application-start-plugins-setup-errors-results-in-lock and that seemed to be down to not enough resources for JIRA to start properly. How much RAM is on the machine running JIRA and how much is allocated to the JVM - http://confluence.atlassian.com/display/JIRA/Increasing+JIRA+Memory ?

Does that help?

Any other errors in the logs?

Andrew.

Jason Varsoke March 18, 2012

Thanks for the tip on memory. I found out swap hadn't been initialized or mounted. So I was trying to load Jira in 8meg. I'm surprised it got so far. I'll try again after correcting the problem when I get home. Thank you so much for responding -- it helps a great deal even if the answer isn't included (though this time it certainly was).

0 votes
Jason Varsoke March 15, 2012

Hmm, can someone please help me? I'm a bit lost here. Is there more information that needs to be provided, or just nobody cares?

Suggest an answer

Log in or Sign up to answer