On 2/27/07, John Gant <email@example.com> wrote:
> Hello all,
> I use eclipse version 3.2.1 buildId M20060921-0945 on osx 10.2 with the
> newest updates. I also use version 1.1.6 of subclipse documentation and
> 1.1.8 for the other subclipse components. I attempt to talk to a
> subversion server (version 1.2.3) running on opensuse 10.1. I estimate
> that out of 10 commits|updates|checkouts 7 freeze and once frozen, cannot be
> canceled without killing the eclipse process. A side note is that I can
> during a freeze, communicate with the subversion server via the command line
> with no issues. Can a network lag cause issues? Is there a log file, or way
> to debug subclipse? Thanks for your help.
If you are in the middle of an operation, then control likely lives in the
Subversion libraries and so Subclipse itself is not freezing. To answer
your question, there is no log you can look at.
When I have seen this problem in the past, the problem has been that the
server was stuck while trying to generate a random number. This was due to
APR on the server being configured to get random numbers from /dev/random
which can apparently hang if the server lacks entropy. To anticipate your
next question, not all server operations require it to generate a random
There are a lot of threads about this on the general
users@subversionmailing list if you want to check the archives.
Finally, Subclipse 1.2.0 is now available and I would recommend it, although
I would not expect it to impact this problem.
Received on Wed Feb 28 00:48:35 2007