Re: [Subclipse-users] ? about this error: org.tigris.subversion.javahl.ClientException: Attempted to lock an already-locked dir

On Nov 25, 2007 5:13 PM, Steve Povilaitis <stevepov@gmail.com> wrote:
> Most exalted ones,
>
> While working remotely over our vpn connection, some of the folks on our
> team get the following error when attempting to update. It doesn't sound
> like a subclipse-specific thing, but I'm hoping one of you may have seen
> this error before and have some idea what it means:
>
> org.tigris.subversion.javahl.ClientException: Attempted to lock an
> already-locked dir
> svn: Working copy 'X:\localrepository' locked
>
> We're using subversion 1.4.5 on a windows host and accessing the
> repository via apache/WebDAV http.

That is the sort of message Subversion typically gives if you perform
an operation AFTER a previous operation has failed. For example,
maybe the VPN tunnel dropped and they got an error. Then they
reconnect the VPN and try update again. Then you will get this
message.

Just use the Team > Cleanup option and it will deal with the locks.
You can then do an update.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org