I ofen get transaction errors when committing. These, as far as I know, are as result of commits that fail halfway through. Is there a way, preferably using a GUI such as TortoiseSVN, that will automatically resume a commit where it failed and will keep retrying until everything is commit?
Example of a failed commit:
Commit failed (details follow): PUT of '/svn/namcloud/!svn/wrk/02b0f9ff-2510-a147-892a-2ee0b7b442dc/src/sites/all/modules/globalredirect/LICENSE.txt': Could not read response body: An existing connection was forcibly closed by the remote host. (http://XXX.XXX.XXX)
It is not entirely automatic, but there is a TortoiseSVN -> Settings... -> Dialogs 2 -> Reopen commit and branch/tag dialog after a commit failed checkbox. This cuts down on the annoyance a bit, automatically resurrecting your log message.
"An existing connection was forcibly closed by the remote host" probably indicates an RST coming back along the TCP/IP connection. This can be generated by anything between you and the remote host.
I'd recommend grabbing something like Wireshark and seeing if there's anything immediately obvious. (This kind of diagnosis is tricky if you're not used to it, but worth a quick look all the same.)
As A.H. suggested, you may want to get in touch with the server administrator. It is possible some evidence of a connection timeout may show up in their webserver or firewall logs, or there may be an immediately obvious timeout setting in e.g. a SSL configuration directive.