Hi Everyone --
We are having some problems using Subclipse with our new SVN server;
any suggestions would be greatly appreciated.
The major symptom is the Eclipse process for SVN actions hanging when
using Subclipse for just about anything: checkout, update, commit,
even simple repository exploring. Sometimes it works great,
committing large transitions and lots of files, other times it gets
stuck updating negligible changes, seemingly without any pattern.
Eclipse is still functional but the SVN action attempted just spins
and spins; the process can't be canceled and terminating Eclipse via
the Task Manager is the only solution. No stack trace or other info
appears in .metadata/.log.
We're SVN newbies and have a generic SVN install, so hopefully there
are some configuration tips and tricks we need to use to make things
go a bit smoother.
Our SVN server setup:
- fsfs (file system) storage type. Berkeley DB (bdb) storage type
kept having lock problems.
- svn+ssh access. We don't run any actual server process running on
the server since svn+ssh does not require or seem to use it.
- everyone uses the same username and password
- Server is Fedora Core 3 Linux and is about 10 feet away on the same network.
- Configuration is vanilla: no hook scripts configured, nothing
changed from the default.
Subclipse Setup:
- JavaSVN
- access via svn+ssh
- have used versions 0.9.37 and 0.9.101. We did get the NPE often
with commits with 0.9.37, but I guess that bug was well known.
Thanks!
-- Joe
Received on Tue Dec 13 17:31:56 2005