We are running Jira 5.0.7 (build 734) with the Subversion plugin version 0.10.10
Our setup has Jira running on a server in our DMZ. It connects to the Subversion repo which is on our SAN in our internal network. Every 2 hours (pretty much precisley) it appears our firewall drops the session between the two. We see this error message when this happens..
2012-12-11 12:38:43,027 QuartzWorker-1 ERROR ServiceRunner Subversion Revision Indexing Service [plugin.ext.subversion.SubversionManagerImpl] Error getting the latest revision from the repository. org.tmatesoft.svn.core.SVNException: svn: E210004: Malformed network data at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readChar(SVNReader.java:478) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.skipWhiteSpace(SVNReader.java:485) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readTuple(SVNReader.java:287) at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:241)
After a period of time (1-7 days ?) our subversion plugin stops working and we have to restart jira to get it working again.
The error displayed at the bottom of tickets (where the subversion information should be) is ..
"Error rendering com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel. Please contact your JIRA administrators".
I tried the patch for 0.10.7 that is listed in https://studio.plugins.atlassian.com/browse/SVN-359
however our Jira fails to start when I use this patch. Does anyone else have any ideas how to resolve this issue (without restarting Jira) ? It would appear to be that the plugin gives up trying to reconnect to the repo ? Even a method of restarting the plugin (via a cronjob etc) without taking down Jira would be good.
The firewall guys would most likley laugh at us If I ask them not to drop sessions indefinitely.
There are various of reason why the error will be thrown. Perhaps checking the Caused by for the trace will give better idea.
For detail logging, you might want to enable the Debug logging for the SVN plugin. Check if the repository is too large, is it always stuck at the same revision number, check if it is really network timeout. By the way, what Subversion version this JIRA connecting to ?
As it turns out, I believe you are actually facing a bug with SVN that is being tracked here:
Some customers mentioned that a restart of the JIRA application resolved the issue, but this is not a confirmed workaround.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG