ALM Subvresion The bundle is uninstalled

We have Subversion ALM installed and configured with 2 repos. After the initial scan, the plugin fails to detect checkins. If we manually run "Scan repositories now" we get the changes. However, waiting for the automatic indexing, we see on the UI our repos colored in Red and show the error message "The bundle is uninstalled"

Any idea on how to fix this? I thought about changing the number of repos which are scanned in parallel to 1 but I do not see where to set that property.

 

Any advice? Thank you Dan

Our logs show the following:

Our logs show the following

 

2015-01-23 15:27:45,120 DefaultQuartzScheduler_Worker-7 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/java failed: The bundle is uninstalled.
2015-01-23 15:27:45,888 DefaultQuartzScheduler_Worker-7 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/sys2 failed: The bundle is uninstalled.
2015-01-23 15:32:45,125 DefaultQuartzScheduler_Worker-8 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/java failed: The bundle is uninstalled.
2015-01-23 15:32:45,911 DefaultQuartzScheduler_Worker-8 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/sys2 failed: The bundle is uninstalled.
2015-01-23 15:37:45,096 DefaultQuartzScheduler_Worker-9 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/java failed: The bundle is uninstalled.
2015-01-23 15:37:45,873 DefaultQuartzScheduler_Worker-9 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://svn.xxxxx.com/svn/sys2 failed: The bundle is uninstalled.

3 answers

Did you get anywhere with this? I'm also having the same issue.... Running the scan manually works fine. Also the scan status indicates that it is running regularly, however commits aren't showing up until explicitly run...

Same problem here since the update to version 6.0.8-jira-6

Problem resolved after a jira service restart

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

654 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot