>> We've been experiencing a sporatic bug (the best
kind of bug) when using the
>> svnClientAdapter. We are actually running a command
line RCP application as
>> part of a CruiseControl build system.
>>
>> Part of this application updates a WC to an old
revision, does some work,
>> then updates it back to the head revision. On these
updates, we sporadically
>> get the following error:
>>
>> Caused by:
>>
org.tigris.subversion.svnclientadapter.SVNClientException:
>> Problem running log
>> svn: In directory 'C: wcsourcexyz'
>> Access is denied.
>> svn: Can't move
>> 'C:wcsourcexyz.svntmpsample.xml.tmp' to
>> 'C:wcsourcexyzsample.xml': Access is denied.
>>
>> Our RCP application is not really all that complex,
and we are performing
>> all operations synchronously (i.e. not kicking off
separate threads that are
>> fighting for resources).
>>
>> I was actually able to reproduce this error a
couple of times in the Eclipse
>> UI by creating a simple toolbar action that did an
SVN update to an old
>> revision, then immediately updated to the head
revision.
>>
>> My guess is that some part of either Eclipse or
Subclipse is holding on to a
>> handle to the sample.xml.tmp file, thus preventing
the move.
>>
>> First, what is this move all about?
>>
>> Second, any ideas what may be holding on to the
temp file, or why it can't
>> be moved?
>
> This would be a general Subversion issue as their API's
do all the
> work. I see this error all the time on their mailing
lists. I
> believe bad virus scanners are the cause. Most people
seem to be able
> to exclude .svn folders or an entire work area.
Thanks for the info,
I've read the posts on the subversion site, and have
disabled all virus scans, as well as Tortoise's icon overlay
process, however I still seem to get the error. The reason
I'm posting back to subclipse is because although the actual
error comes from subversion, I thought the cause of the
error may actually come from either subclipse or eclipse.
When an update is done via subclipse, I believe the
OperationManager creates another thread (WorkspaceRunnable?)
to fire off resource change events for .svn directories.
Subclipse has resource change listener that will handle
these resource change events and update it's status cache
(?). I'm assuming that this will load various
files/resources to update it's cache. Since this is done
asynchronously, the initial thread could perform another SVN
operation, thus conflicting with the status cache reads.
Does this sound at all feasible?
------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribe subclipse.tigris.org
For additional commands, e-mail: users-help subclipse.tigris.org
|