Community
Participate
Working Groups
Since some weeks ago I and my team keep getting error like this: Synchronize operation failed. svn: Received fatal alert: bad_record_mac svn: PROPFIND request failed on '/svnroot/modeling/org.eclipse.emf.cdo/!svn/bln/8207' The paths that cause this problems are constantly varying but they're all under /svnroot/modeling/org.eclipse.emf.cdo I have no clue if this is a Subversive tool problem (all my committers seem to have this problem) or a server file system problem (caused by the recent crash/outage?). But it starts to become very annoying and I'd like to start somewhere...
Bug 207175 reports a *similar* issue, but they say it's "SSL3 related" and I can make no sense out of it.
And there's http://www.eclipse.org/forums/index.php/m/633941
A quick Google search reveals that this problem is manifested with other repositories, not just Eclipse's. I thought this was interesting: http://www.thatsjava.com/java-tech/73075/ "Have a look at bug 4513263, http://developer.java.sun.com/developer/bugParade/bugs/4513263.html The key for me in fixing the bad_record_mac problem was a one-liner fix to disable TLS by calling: socket.setEnabledProtocols(new String[] {"SSLv3"}); Hope this fixes it for you..." Which SVN client are you using?
(In reply to comment #3) > Hope this fixes it for you..." Was that still part of the citation or do you mean me? > Which SVN client are you using? Subversive, both directly in the IDE and as Buckminster plugin. Both have shown this error. Frequently.
It was part of the citation. Bug 207175 alludes to a problem with HttpClient. If Subversive uses HttpClient, then there could be a bug way upstream. http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/200902.mbox/%3CCE1A701EDAB9A447B24DD8045832F67E4C97D89302@FRSPX100.fr01.awl.atosorigin.net%3E Some of these discussions look fairly old; I wonder why we're still seeing this. Is there any way of just trying another SVN client?
> Is there any way of just trying another SVN client? I experience this kind of error on other svn repositories, too when I use subversive. I did not track the cause down to a specific use case but I pretty much believe that it mostly happens when deleting and refactoring (rename) resources. IMHO this is a bug in subversive since it never happens to me when using Subclipse or the command line svn client. Unfortunately (at least when I tried this the last time > 1y ago) you cannot switch from subversive to subclipse on the fly, you have to do a fresh checkout.
(In reply to comment #5) > Is there any way of just trying another SVN client? I agree with André that's not so easy and certainly no long term solution ;-( Should we move this bug to Subversive and see if they have an idea?
I told Eike per EMail that I can reproduce the problem when setting up a fresh CDO source workspace as described in the wiki. The Buckmister Import function gives several of the "bad mac" errors. This seems to be a bug in SVNKit (and thus, this bug most likely affects Polarion or an upstream component). Here's what I did to try out a workaround: - Go to install software - Switch to the Polarion SVN connector update site - Select the JavaHL 1.6 SVN connector - Install it - Go to preferences, Team, SVN - Switch SVN connector from SVNKit to JavaHL (I'm on a Mac and got svn binaries available on command line, Windows users might have to install some native SVN client). Now my errors are gone. The only thing I changed is the SVN connector. I still use the Subversive Team Provider, I just don't use SVNKit anymore...
(In reply to comment #8) I tried the JavaHL Connector but then it turned out that I need to providesome native library and that is not available for my 64 bit platform. Seems that's no solution for me ;-(
Correction: I was able to install a 64-bit version of the native binaries with the help of http://subclipse.tigris.org/wiki/JavaHL#head-0ae839721445e3f59d10a128ec9439d4f4988d5f At least it seems to work now. Will report when I'm sure that the original trouble is past...
By chance, I came over a tweet just now: @jtpadilla (Juan Padilla Julian) Si tienes problemas con tu servidor SVN por SSH debido al numero de conexiones prueba con "-Dsvnkit.ssh2.persistent=false" en "eclipse.ini" I don't speak spanish, but I interpret "If you have problems with SVN and SSH, try putting "-Dsvnkit.ssh2.persistent=false" in your "eclipse.ini" file. I've tried the SVNKit again with this option and indeed: it works!
That would be great news. Actually I'm still happy with the JavaHL connector as you've suggested first! That said, I'm quite unhappy with Subversive/SVN speed. I've spent a couple of hours for a single merge of the entire trunk to maintenance. Several freezes followed by cancel, restart Eclipse and retry. And that although I was already doing Caspar's trick of using a complete trunk checkout rather than Buckminster's many separate project checkouts. I'm thinking about Git again...
I think with the two approaches Stefan's posted we can close this bugzilla.
Good to see the cooperation here.
Just a note: Subversive always forgets about my connector setting after each restart! Crap!
Movng to Subversion component.
