[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Checkout causing server to crash

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 19 Feb 2015 15:40:48 -0500

On Thu, Feb 19, 2015 at 2:37 PM, Jacob Weber <jacob_at_jacobweber.com> wrote:

> Here's a strange one.
> When i check out a certain project using Subclipse, the SVN SERVER runs
> out of memory and the process gets killed by oom-killer.
> It only happens when I specify a revision (rather than HEAD), but it
> happens with several different revisions.
> The surprising thing is that this happens with SVNKit AND JavaHL (SVN
> 1.8.5). But when I try the same thing on the same command line SVN client,
> there's no problem:
> svn checkout svn+ssh://user@host/repo/project/branches/foo -r 123456
> --depth=infinity --force
> When it happens, nothing appears in the SVN console (not even the
> "checkout" command). The task in Progress says "Checking out foo:". It
> hangs for 5-10 minutes, then the server breaks the connection, and
> Subclipse shows this error:
> Failed in RemoteResource.getLogMessages()
> org.apache.subversion.javahl.ClientException: APR does not understand this
> error code
> svn: ra_serf: The server sent a truncated HTTP response body.
> It happens with both svn+ssh and https.
> I'm using Eclipse 4.4.1, with all updates, and Subclipse 1.10.9, on Mac OS
> X. A colleague with the same setup, but running Debian, has the exact same
> issue.

It is ultimately the responsibility of the server to manage its memory and
not crash etc. Since you can reproduce this with https, I would focus on
that since it offers better logging. Turn on the SVN operational logging
if possible and try to find out what "commands" the server is receiving.

> Failed in RemoteResource.getLogMessages()

This is odd. I cannot think of why the checkout process would call this.
Perhaps you have the History view showing somewhere with the Link to Editor
feature active and something is triggering that view to also make a call to
the server to fetch history? That said, I fail to see why running checkout
and a history call at same time would be an issue for the server.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2015-02-19 21:40:57 CET

This is an archived mail posted to the Subclipse Users mailing list.