|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Re: checkout & locking: problemjust saw the lines wrapped. attached the file with the traces.
========= Hi! recently we decided to upgrade our application from svnkit 1.1.7 to 1.3.0. We updated the library, adjusted the code to the new API and imagine our surprise when we got many problems! Basically, everything we try to do results in the same error, below are two examples. SVNKit complains about the wc being locked, which it isn't. I've checked with the commandline subversion tooling. I googled at bit and only found something similar to a bloke having issues on OpenVMS. We are at WinXP and Win2003 anybody knows whether this is a bug or are we doing something wrong? -- ir. Ferry Huberts Pelagic Bonairepier 28 1339 KH Almere tel: +31.6.54.93.51.31 20:21:42,109 Error while checking out '/' [ main] ERROR xxxxxx 04 Sep 2009 20:21:42,109 org.tmatesoft.svn.core.SVNException: svn: Working copy 'D:\Program Files\xxxxxx\.\store\Configs\Current\' locked; try performing 'cleanup' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.lock(SVNAdminArea14.java:1552) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:359) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:263) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:256) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:151) at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:417) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:875) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:732) at xxxxx 20:39:08,112 Error while reverting '/' [ main] ERROR xxxxxx 04 Sep 2009 20:39:08,112 org.tmatesoft.svn.core.SVNException: svn: Working copy 'D:\Program Files\xxxxxx\.\store\Configs\Current\' locked; try performing 'cleanup' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.lock(SVNAdminArea14.java:1552) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:359) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:263) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:256) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:151) at org.tmatesoft.svn.core.wc.SVNWCClient.doRevert(SVNWCClient.java:1752) at org.tmatesoft.svn.core.wc.SVNWCClient.doRevert(SVNWCClient.java:1685) at xxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: svnkit-users-unsubscribe@... For additional commands, e-mail: svnkit-users-help@... |
|
|
Re: checkout & locking: problemHello Ferry,
Can you try the latest trunk version of SVNKit that can be downloaded from our build server at http://teamcity.svnkit.com (log in as a guest, then download binaries from artifacts of the trunk configuration). If the problem stays with this version, can I ask you to send a wc, where this problem can be reproduced during revert operation? Thank you. Regards, ---- Alexander Sinyushkin, TMate Software, http://svnkit.com/ - Java [Sub]Versioning Library! Ferry Huberts wrote: > just saw the lines wrapped. attached the file with the traces. > ========= > Hi! > > recently we decided to upgrade our application from svnkit 1.1.7 to 1.3.0. We > updated the library, adjusted the code to the new API and imagine our surprise > when we got many problems! Basically, everything we try to do results in the > same error, below are two examples. > > SVNKit complains about the wc being locked, which it isn't. I've checked with > the commandline subversion tooling. > > I googled at bit and only found something similar to a bloke having issues on > OpenVMS. > We are at WinXP and Win2003 > > anybody knows whether this is a bug or are we doing something wrong? > > > > ------------------------------------------------------------------------ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: svnkit-users-unsubscribe@... > For additional commands, e-mail: svnkit-users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: svnkit-users-unsubscribe@... For additional commands, e-mail: svnkit-users-help@... |
|
|
Re: checkout & locking: problemOn Mon, September 7, 2009 21:03, Alexander Sinyushkin wrote:
> Hello Ferry, > > Can you try the latest trunk version of SVNKit that can be downloaded > from our build server I did and still have the problem. > > If the problem stays with this version, can I ask you to send a wc, > where this problem can be > reproduced during revert operation? > the primary problem is in the checkout. we first checkout a wc before starting to work on it. the checkout already fails. I have attached some more files. I have directed the svnkit logging to our error log and what I find especially strange is the error store\Configs\Current\.svn\entries (The system cannot find the path specified) The file _is_ there and can be read just fine. Maybe the code can no longer handle relative paths? Or the contents of the file are not correct? --------------------------------------------------------------------- To unsubscribe, e-mail: svnkit-users-unsubscribe@... For additional commands, e-mail: svnkit-users-help@... |
|
|
Re: checkout & locking: problemHello Ferry,
One could get "working copy is locked" error when tries to change working that is locked (doesn't explain anything :)) - which means technically that there is an empty "lock" file (file named "lock") in .svn directory. This file is created when SVNKit (or Subversion) starts write operation on a working copy. Then, directories in scope of the operation are "locked". When operation completes normally, lock files are deleted. In case operation is interrupted, lock files remains in place. To remove lock files you have to run "cleanup" operation, either with command line client ([j]svn cleanup) or with SVNKit API (SVNWCClient.doCleanup(...)). In very rare cases cleanup doesn't help (when there are also journal files left which couldn't be executed for some reason). Then the only way to resolve the problem is to do a fresh check out of a working copy. You wrote the checkout fails. Are you trying to check out to the folder that already contains ".svn" directory? Try to check out to the directory that doesn't exist prior to checkout. Alexander Kitaev, TMate Software, http://svnkit.com/ - Java [Sub]Versioning Library! http://sqljet.com/ - Java SQLite Library! Ferry Huberts wrote: > On Mon, September 7, 2009 21:03, Alexander Sinyushkin wrote: >> Hello Ferry, >> >> Can you try the latest trunk version of SVNKit that can be downloaded >> from our build server > > I did and still have the problem. > >> If the problem stays with this version, can I ask you to send a wc, >> where this problem can be >> reproduced during revert operation? >> > > the primary problem is in the checkout. we first checkout a wc before starting > to work on it. the checkout already fails. > > I have attached some more files. > I have directed the svnkit logging to our error log and what I find especially > strange is the error > > store\Configs\Current\.svn\entries (The system cannot find the path specified) > > The file _is_ there and can be read just fine. > Maybe the code can no longer handle relative paths? > Or the contents of the file are not correct? > > > ------------------------------------------------------------------------ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: svnkit-users-unsubscribe@... > For additional commands, e-mail: svnkit-users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: svnkit-users-unsubscribe@... For additional commands, e-mail: svnkit-users-help@... |
|
|
Re: checkout & locking: problem>
> One could get "working copy is locked" error when tries to change > working that is locked (doesn't explain anything :)) - which means > technically that there is an empty "lock" file (file named "lock") in > .svn directory. > > This file is created when SVNKit (or Subversion) starts write operation > on a working copy. Then, directories in scope of the operation are > "locked". When operation completes normally, lock files are deleted. In > case operation is interrupted, lock files remains in place. thanks for the explanation. but I already know that :-) the directory in which the checkout is done is freshly created by the application. I already ensured that we got back to the most basic usage. --------------------------------------------------------------------- To unsubscribe, e-mail: svnkit-users-unsubscribe@... For additional commands, e-mail: svnkit-users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |