Re: DB error after simultaneous accesses

At 7:16 PM +0200 9/9/03, Grundberg Michael wrote:
>Hi,
>
>I've just starting migrating a few of my company's projects into
>Subversion but I ran into a couple of problems. I'm running
>subversion 0.28.2 on win2k. The client (only me so far) is accessing
>the repository residing on the server via Apache 2.0.47.
>
>I created a repos, added a couple of dirs and made a commit. All
>fine. Then I copied about 60 megs of source files into a working dir
>and issued svn add. Then I committed and watched alot of dots flying
>by... After a couple of minutes I got bored so I opened another
>shell and issued an svn log in a working dir different from the
>first. This caused the newly issued svn command to hang, as did the
>first commit.

This (and the rest of your description) sound to me hauntingly like
the "run out of locks" problem (issue 1499), which is being actively
worked even as we speak. Perhaps one of the folk more knowledgeable
in 1499 can confirm or deny that?

If so, it's a known problem, should be fixed soon, and in the mean
time, "don't do that" ;-)

>Also, shouldn't one be able to perform two accesses to the server
>simultaneously? (As I did with commit / log) At the least, the first
>commit shouldn't time out, should it?

Absolutely, what you did *should* work. As you noticed, it *doesn't*
work at the moment, but that's merely a bug.

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org