nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Subversion plugin unable to load Subversion tab

Jayvijaysinh RA

We have configured the JIRA Subversion plugin with 2 SVN repositories.

It was working find until few days back we started facing issues that Subversion tab is not rendered on the JIRA issue.

When we had a look at the JIRA logs we found the below errors.

2014-03-24 09:23:59,257 http-bio-17500-exec-10649 ERROR Test@user 563x699605x1 d1n1s0 10.140.7.246 /browse/NEXT-26 [jira.plugin.issuetabpanel.IssueTabPanelInvokerImpl] Exception thrown while trying to call getActions() for com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel (Show Subversion commits related to an issue in an issue tab panel.)
com.atlassian.jira.InfrastructureException: org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 290
svn: E175002: PROPFIND of '/svn-ags/next/!svn/vcc/default': 500 Internal Server Error (http://svn.paas.intraxa)
at com.atlassian.jira.plugin.ext.subversion.SubversionManagerImpl.getLogEntry(SubversionManagerImpl.java:177)
at com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexer.getLogEntriesByRepository(RevisionIndexer.java:525)
at com.atlassian.jira.plugin.ext.subversion.issuetabpanels.changes.SubversionRevisionsTabPanel.getActions(SubversionRevisionsTabPanel.java:69)
at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanel3Adaptor.getActions(IssueTabPanel3Adaptor.java:45)
at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelInvokerImpl.invokeGetActions(IssueTabPanelInvokerImpl.java:81) <+2> (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)

When we had a look at SVN revisions, the latest revision was 248, so there were no revision exist with 290.

Now we think revision 290 might have been deleted so we are not able to locate it in SVN, so how to prevent such cases? Now how to solve this problem of Subversion tab fails to render.

Shall we uninstall Subversion plugin and install again to refresh the cache? Will this solve our problem?

How to deal with such issues in future?

regards,

Jay

Accepted answers

All comments

Norman Abramovitz

You will need to re-index the subversion plugin. There are directions on how to re-index in the documentation.

Jayvijaysinh RA

Could you please send me the document link or any steps how to do it.

I tried searching it and it says need to delete the cache folder and restart JIRA

/indexes/plugins/atlassian-subversion-revisions

But is there any better way? I cannot afford to restart JIRA at the moment.

Norman Abramovitz

https://ecosystem.atlassian.net/wiki/display/SVN/Subversion+JIRA+plugin;jsessionid=C1A4FF07DD570DBD71A9300D85D151EE

Read the Upgrade Instructions paragraph and then read step 5 for the uninstall instructions.

Stop Jira
- Make sure Jira is really stopped. If you are running windows and using a service, make sure the service is actually stopped. The command line script generally completes but Jira is still shutting down.
Do Step 5 (remove the index directory)
Start Jira

Contact Kintosoft

Sure does JIRA need to be re-started?

The latest versions of the Atlassian's plugin support the V2 plugin model, it means disabling the plugin should fully unload it from memory and therefore the Lucene index files would be unlocked and then they could be deleted without any problem.

I guess these instructions are a bit old and they refers to the older versions (V1 plugin model), when plugins could not be undloaded from memmory and stopping JIRA was the only way to unlock resources.

Norman Abramovitz

I had issues with indexing not restarting with enable and disable. We also do not know which version of the Atlassian plugin this person is using.

Jayvijaysinh RA

Hi Guys,

Thanks a lot for your interesting replys.

Here are the details of my environment.

JIRA version : 6.0

Subversion Plugin version: 0.10.13

Running on Linux Redhat 6 with Tomcat 7

The Universal Plugin Manager (v2.10.1) by Atlassian

Now could you please confirm that I do not need JIRA restart.

regards,

Jay

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

app

svn