Unable to Start JIRA when Subversion is Installed
Symptoms
- JIRA is unable to start and crashes when the Plugin System starts.
- JIRA hang while Plugin System starts to load Subversion Plugins
The following appears in the atlassian-jira.log:
2012-05-29 19:22:34,396 main ERROR [atlassian.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/internal/io/dav/DAVRepositoryFactory
at com.atlassian.jira.plugin.ext.subversion.MultipleSubversionRepositoryManagerImpl.<init>(MultipleSubversionRepositoryManagerImpl.java:69)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
...
Caused by: java.lang.ClassNotFoundException: org.tmatesoft.svn.core.internal.io.dav.DAVRepositoryFactory
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
... 50 more2013-01-10 16:59:03,331 localhost-startStop-1 ERROR [plugin.ext.subversion.SubversionManagerImpl] Connection to Subversion repository https://subversion.xxxxx.com/svn/XXXX failed: org.tmatesoft.svn.core.SVNException: svn: E175002: CONNECT request failed on 'http://proxy-xxxx:8080'
svn: E175002: CONNECT of 'subversion.xxxxx.com:443': 503 Service Unavailable (https://subversion.xxxxx.com)
org.tmatesoft.svn.core.SVNException: svn: E175002: CONNECT request failed on 'http://proxy-xxxx:8080'
svn: E175002: CONNECT of 'subversion.xxxxx.com:443': 503 Service Unavailable (https://subversion.xxxxx.com)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:106)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:90)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:187)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:343)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:286)Cause
- An incompatible version of the Subversion plugin has been installed for the current JIRA version.
- Proxy configuration was used with JIRA and subversion plugin can't reached the server
- A repository that configured with the plugin is unreachable
Resolution
Incompatible Version
- Uninstall the JIRA Subversion plugin, as in the Uninstall Instructions.
- Download the latest plugin version for the JIRA version, as on the Atlassian Marketplace.
Install that plugin as described in the Install Instructions.
If you experience any additional problems with the plugin, please follow the Troubleshooting Instructions or raise a support ticket on support.atlassian.com.
Proxy Configuration
If you're using proxy configuration with JIRA, add nonProxyHost parameter to bypass the subversion server. Referring to the Java Startup Option on how to set the parameter.
-Dhttp.nonProxyHosts="atlassian|localhost"
Unreachable Repository
In the case that a repository is unreachable, JIRA will try to connect to the repository until a timeout is reached. This will happen for every repository that is unreachable which means that you may have to wait awhile in order for JIRA to fully spin up.
The following query will list your configured repositories.
select * from propertyentry pe,propertystring ps where pe.id = ps.id and entity_name like '%subversion%';