Subversive Commit Issues

Classic Servoy
1

We recently opened the port to our SVN Server (v1.3.2) to the internet. We can successfully checkout a solution, but the commit is failing. There are a couple different errors I have seen. We are using Subversive 2.0.7.

From inside the office, on the LAN accessing the SVN Server via the external URL (e.g. svn://myserver.com), I get

Some of selected resources were not committed.
svn: Commit failed (details follow):
svn: Connection reset

From outside the office, OFF the LAN accessing the SVN Server using the same URL, I get

Some of selected resources were not committed.
svn: Commit failed (details follow):
svn: Malformed network data

I’ve searched on Google and in the Servoy forum, but I am not really getting any clues as to what might be happening.

Can anyone help?

2

connetion reset means that the other side (the server) killed your connection.

Or something is in between that somehow touches your connections, is there for example a proxy inbetween?

3

I understand that the server killed the connection. What I am uncertain of is why? Our setup includes a proxy server (Microsoft ISA Server 2000) which redirect all traffic on port 3690 to the SVN server. Since we can perform a checkout and an update without issues, I’m left scratching my head as to why we can’t commit. It seems that something is blocking the inbound “data,” but not the outbound data. Soes Subversive use another port besides 3690 during a commit?

4

We recently moved to SVN using subversive as well.
I can subscribe that just port 3690 had to be opened up on our router which routes the external ip to our SVN server for port 3690 traffic.
We didn’t find any issue, it even doesn’t look slower when I’m committing changes from outside the office.

Can you temporary get around your proxy? Just to test if this might be the thing that causes you trouble?

5

does it somehow also monitor (firewall) the connections?
maybe the proxy/firewall drops because some packages are not allowed?

i also would try without the proxy somehow to see if it is that or not.

6

This issue is solved. It turns out to be a bug in SVNKit. To correct the issue, launch Servoy and set the preference. Window->Preferences->Team->SVN->SVN Connector. Change the SVN Connector to Native JavaHL (svn:1.5.4).

Thanks to everyone who sommented on this issue!

7

We also had several weird SVN issues with Subversive/SVN. Just to be save we also moved to JavaHL and let it use the native Subversion binaries.
For anyone that wants to do the same, just download and install Subversion on your development machine and install the JavaHL plugin in Eclipse. As JT explained you should see JavaHL as a SVN connector in the preferences.

Hope this helps.

8

under windows you dont need to have to install a native client with subclipse because there the JavaHL plugin and native code is shipped as a plugin. (only 32 bit by the way, so for windows 64 bit you need to use SVNKit or get a 64bit binary from somewhere… )