Bugzilla – Full Text Bug Listing
| Summary: | Malformed network data during synchronization | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Brendan <bberry> |
| Component: | Core | Assignee: | Igor Burilo <igor.burilo> |
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | a.gurov, ceagan, egalvez, kaabab, reckord, tonny.madsen |
| Version: | 0.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
Could you please provide some more details: 1) SVN server version? 2) protocol? 3) is there any proxy? 4) if it is secure protocol is there any specific to it? 5) is server you working with remote or local and how fast could it be accessed (just to be sure about potential race conditions)? 6) Anything else you think could be important? Then I will file bug report to the SVN Kit developers tracker. Hm, I'm asking about SVN Kit because I've heard something similar already. So if I'm wrong and you're using native JavaHL-based one, then please correct me. 1) svn, version 1.6.6 (r40053) 2) svn+ssh 3) we have a proxy for accessing external addresses only 4) we use the standard openssh-server from ubuntu Version: 1:5.3p1-3ubuntu5 5) the server is on our local area network. if we use the debugger and drop to stack when the IOException occurs, the problem appears to go away while stepping through the code, so this is likely due to a race condition. 6) We see the error on Eclipse clients and on our Buckminster builds running on Jenkins. These builds are on the same server as SVN but still connect using svn+ssh and the error occurs more reproducibly there. Thank your for your information. I have created corresponding issue report in the SVN Kit tracker: http://svnkit.com/tracker/view.php?id=404 Also if it is possible you can try http or https protocols in order to avoid the issue. Alex, can you push the svnkit people a bit? In our organization we are getting this a lot, makes Eclispe 3.6 SR2 look bad... I can't push anyone, but I've asked if there is a need of some more information from our side in order to speedup solving the issue. But is there really no way to avoid the problem in your case (changing protocols or temporarily switching to the JavaHL-based connector)? I have this problem as well. I cannot change protocol as this is used for outside access to some of my customers. And I cannot change to JavaHL as I use a MAC... For additional color: we ship a product to our customers, where we include as a convenience, the SVN team connector. Best practices and most googling around will lead anyone to believe SVNKit is the preferred connector (being pure Java and all that). Could you maybe (re-)add a Connector for an older 1.3.x SVNKit version to the connectors list? The 1.3.2 version org.polarion.eclipse.team.svn.connector.svnkit16 2.2.2.I20100512-1900 seems to have worked fine. I tried installing that one into my eclipse with an otherwise up-to-date SVN Team Provider. It seemed to install fine, but it doesn't show up in the list of installed connectors. I guess that connector and team provider plugin versions are tightly coupled? We are anxious for a better solution, but for those of you facing this problem, one solution that worked for us was to download the archived update site for Helios (Subversive-incubation-0.7.9.I20100512-1900.zip) from http://www.eclipse.org/subversive/downloads.php and then download the old connectors that went with that version (Subversive-connectors-2.2.2.I20100512-1900.zip) from http://community.polarion.com/projects/subversive/download/eclipse/2.0/builds/ We install these by first installing everything from the incubation archived update site, then restarting Eclipse, cancelling the automatic connector installation dialog, an installing the latest SVNKit 1.3 Connector from the connectors archived update site. Of course, this sets you back to the Helios release version and won't include any bugfixes for other issues made since then, but it makes svn+ssh on the LAN work for us. (In reply to comment #9) > Could you maybe (re-)add a Connector for an older 1.3.x SVNKit version to the > connectors list? > > The 1.3.2 version org.polarion.eclipse.team.svn.connector.svnkit16 > 2.2.2.I20100512-1900 seems to have worked fine. I tried installing that one > into my eclipse with an otherwise up-to-date SVN Team Provider. It seemed to > install fine, but it doesn't show up in the list of installed connectors. I > guess that connector and team provider plugin versions are tightly coupled? Yes, they're actaully tightly coupled. And about adding an SVN Kit connector for the 1.3.2 client library version - that is a nice idea and we will think of it. It just that it requires creating a new connector, because SVN Kit 1.3.2 have no support for some of the features implemented in last months. The older SVN Kit 1.3.3 version will be returned in the build on this week just to cover the issue. (In reply to comment #12) > The older SVN Kit 1.3.3 version will be returned in the build on this week just > to cover the issue. After some work with a ...svn.feature.group, this seems to work. Thanks... |
Running the latest build of Subversive (0.7.9.I20101203-1700), I frequently encounter this error while trying to synchronize, commit, or update. The error log includes the following output (but no stack trace): ERROR [0006] : Resolution attempt ended with exception: java.io.IOException: svn: Malformed network data ERROR java.io.IOException: svn: Malformed network data ERROR java.io.IOException: svn: Handshake failed, received: The error goes away after reverting to the previous version (0.7.9.I20100512-1900). This is happening on every machine to which we have installed Subversive. The problem is intermittent, but occurs frequently enough that we generally can't successfully synchronize more than two or three projects at a time.