JIRA Subversion plugin cannot be enabled

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms:

JIRA Subversion plugin is disabled automatically via UPM and the following appears on atlassian-jira.log or catalina.out: 

1 plugin failed to load during JIRA startup.
    'com.atlassian.jira.plugin.ext.subversion' - 'JIRA Subversion plugin'  failed to load.
        Cannot start plugin: com.atlassian.jira.plugin.ext.subversion
            Unresolved constraint in bundle com.atlassian.jira.plugin.ext.subversion.atlassian-jira-subversion-plugin [77]: Unable to resolve 77.0: missing requirement [77.0] package; (&(package=com.google.common.collect)(version>=11.0.2.atlassian-01))
        It was loaded from C:\Program Files\Atlassian\Application Data\JIRA\plugins\installed-plugins\plugin_441414568354244795_atlassian-jira-subversion-plugin-2.x.x.jar
2015-09-04 09:15:16,447 http-bio-80-exec-32 ERROR spiderman 550x932969x1 xxx 0:0:0:0:0:0:0:1 /rest/plugins/1.0/com.atlassian.jira.plugin.ext.subversion-key [atlassian.plugin.manager.PluginEnabler] Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.jira.plugin.ext.subversion

Cause 1:

The JIRA Subversion plugin versions 2.x are not compatible with JIRA 6.2 and below, as stated on the Subversion version history page.

Cause 2:

The problem happened after upgrading JIRA to 6.4.x where some of the broken repositories are stored in the database. Moreover, the logs is showing this kind of error message:

Invocation of init method failed; nested exception is com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/ietf/jgss/GSSException
java.lang.NoClassDefFoundError: org/ietf/jgss/GSSException
org/ietf/jgss/GSSException
org.ietf.jgss.GSSException

To diagnose the problem, please run the SQL query below and verify which repos are not valid or broken:

SELECT * FROM propertyentry LEFT JOIN propertystring ON propertyentry.ID = propertystring.ID WHERE PROPERTY_KEY like 'svn.root';

Cause 3:

Misconfiguration in JVM arguments where it doesn't support or compatible with the current Java version. The JVM information can be check in Setting Properties and Options on Startup.

Resolution 1:

Any one of the following procedures can solve this problem:

  • Install the JIRA Subversion plugin version 1.0 if you need to stay on your current JIRA version.
  • Upgrade JIRA to a version compatible with the plugin version as per the Subversion version history page.

Resolution 2:

If there is any broken repos URL from the results, you may delete the entries using this SQL query:

DELETE FROM propertystring WHERE id = '<entries_id>';
tip/resting Created with Sketch.

We recommend test it in a staging environment or backup JIRA in advance before execute the query.


Resolution 3:

If you are using JDK 1.7 or 1.8, please remove the -Dsvnkit.http.sslProtocols=SSLv3 parameter from JVM arguments. 


Last modified on Nov 16, 2018

Was this helpful?

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