JIRA Subversion Plugin: "The call to the JIRA server did not complete within the timeout period."

Still need help?

The Atlassian Community is here for you.

Ask the community


After starting (or restarting JIRA), the JIRA Subversions Plugin cannot be enabled.  In the UI, the following error may appear with the message "The call to the JIRA server did not complete within the timeout period.  We are unsure of the result if this operation":


The following appears in the atlassian-jira.log:

2014-10-27 10:31:45,277 Spring executor 22 ERROR rutherford 628x623115x5 1lr1o54 /rest/plugins/1.0/com.atlassian.jira.plugin.ext.subversion-key 
[plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository failed: 
org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for '<> TEST SVN'


The JIRA instance contains SVN repositories that cannot be reached during startup phase which disables the plugin due to timeouts. Trying to enable the plugin at a later stage fails as well.

SVN-435 - Getting issue details... STATUS has been logged as a regression bug that describes a problem authenticating with subversion repositories using Active Directory.  If your subversion repository uses Active Directory to authenticate, please review the bug report and give the listed workaround a try.  


Remove the repository information from the JIRAdatabase and then reconfigure them in the plugin once you are able to get it started up.  If possible, we strongly suggest you try this in a test environment first.  Also, since it involves direct database manipulation, you will want to take a backup of your data before attempting in your production instance in the event that you need to revert back to your prior state.

  • Determine how many repositories you have configured:  Run this SQL to see your current configurations. This is a step designed to inform you of how many repos you are dealing with and to give you a sense of what you will need to reconfigure once the plugin is able to be configured.

    select * from propertyentry pe,propertystring ps where pe.id = ps.id and entity_name like '%subversion%';

    Having this information is also helpful in potentially identifing problematic repositories. If there is a repository that has been configured in JIRA that has known issues, you could try addressing that specific repo depending on what the known issue is.

  • Delete your repo data from the db:
      • Shut down JIRA.
      • Run this SQL:

        delete from propertystring 
        where ID in 
        	(select ID from propertyentry where entity_name like '%subversion%');
        delete from propertyentry where entity_name like '%subversion%';
      • Restart JIRA.
      • Try to enable the JIRA Subversion Plugin
      • If it enables, reconfigure your repository information

Help us improve!

Last modified on Aug 14, 2015

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.