Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

got an error Cannot autowire object because the Spring context is unavailable. Ensure your OSGi bundle contains the 'Spring-Context' header.

yariv golan November 4, 2012

using Jira 5.1 i have installed Behaviours, i when to the administrator dceen click on Behaviours then got this error:

Cannot autowire object because the Spring context is unavailable. Ensure your OSGi bundle contains the 'Spring-Context' header.

Could not find what you were looking for. Maybe you should raise an issue.

what is it?

Ya.

3 answers

0 votes
Joanna (Yahoo)
Contributor
January 14, 2013

I have the same problem on JIRA v5.2.1 and Behaviours Version 0.5.3. I installed from UPM without problems but I get the above error when trying to access the Behaviours config page. Jamie - can you help resolve?

Joanna (Yahoo)
Contributor
January 14, 2013

This is now resolved. But prudent administrators, read on.

In trying to fix/troubleshoot this further, I noticed that the JIRA UPM had an 'Update Available' and foolishly thinking it was harmless to let it update itself :-), I clicked the button. UPM started updating, then JIRA chocked and died. Had to restart JIRA. Good news is that it did come up. UPM now shows the 2 entries (Atlassian Universal Plugin Manager Plugin and Atlassian Universal Plugin Manager Self-Update Plugin) which weren't there before. AND moreover... Behaviours plugin miraculously works! ;-) That leads me to believe either of 2 things... something in the UPM update fixed the Behaviours plugin issue OR the restart itself fixed it. Not sure. Either way, it works now. But Jamie, if you have any further info, your response is welcome :-)

JamieA
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.
January 14, 2013

Sorry, yes, it requires a restart when you have this problem with the behaviours plugin. Have never been able to reproduce this problem myself... must be an interaction with another plugin.

0 votes
yariv golan November 4, 2012

jira 5.1.5 plugin version 5.0.2

JamieA
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.
November 4, 2012

I guess you mean 0.5.2. That combination works for me... can you give me more info:

Were you upgrading
Can you create a support request on https://studio.plugins.atlassian.com/browse/JBHV attaching the full jira log from a restart?

thanks

yariv golan November 4, 2012

I didn't upgrade, freash installation, as for the restart, i can't do restart for all projects.

Yariv

0 votes
JamieA
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.
November 4, 2012

What exact version of jira? What version of the plugin?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events