This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 125573 [details] message log Product Version: NetBeans IDE 7.3 Beta (Build 201210011125) Java: 1.7.0_05; Java HotSpot(TM) 64-Bit Server VM 23.1-b03 System: Linux version 3.2.0-32-generic running on amd64; UTF-8; en_US (nb) svn, version 1.7.6 (r1370777) Number of actions (resolve conflict, update, etc) will cause following exception to be thrown: org.apache.subversion.javahl.ClientException: E200030: BUSY Since Subversion 1.7 any write operation locks .svn/wc.db database. Sounds as if there is a background process accessing the working or as if the client is accessing working copy from several threads causing E200030: BUSY to be thrown.
attach a thread-dump so i can identify the pending thread.
Created attachment 125589 [details] thread dump
Created attachment 125590 [details] thread dump I think that the first one uploaded will be more useful. Let me know if I could assist further please.
Can you run any svn command directly in shell with a commandline client? If you can, provide exact steps to reproduce, i cannot reproduce. It's probably a bug in SVNKit anyway, however i cannot file a bug without reliable steps to reproduce.
as the last resort, does it help to restart the IDE?
(In reply to comment #5) > as the last resort, does it help to restart the IDE? grrr.... I restarted IDE before you posted comment(s) and now I cannot reproduce it. :( I was able to run commands from shell. Lets close the issue. If I bump into it again I will reopen it.
(In reply to comment #6) > Lets close the issue. If I bump into it again I will reopen it. If you reproduce it, try to describe what you were doing. I might have seen it once or twice while playing with svn working copies in the past but the reason for the lock-down was probably such a rare race condition i was unable to reproduce again.
(In reply to comment #7) > (In reply to comment #6) > > Lets close the issue. If I bump into it again I will reopen it. > If you reproduce it, try to describe what you were doing. I might have seen it > once or twice while playing with svn working copies in the past but the reason > for the lock-down was probably such a rare race condition i was unable to > reproduce again. I just hit it again. I can't reproduce it still but at least I have idea when it might happen. I have a load of work. I will try to reproduce over the weekend.
Just got the same thing again. First time out of 80 commits through netbeans. I'm on Windows, using last netbeans version. That's what i did: - There were 74 editions/deletions/additions. - I clicked Commit all, entered a commit text, and clicked OK. - After one second, i got the "SVN copy not up to date" message. - In command line, i threw a "svn up" (i'm the only one to work on it so it wasn't about receiving any changes, it has just output "Updating '.': to revision 80". - Back in netbeans because i didn't want to loose my long commit message, i click commit all again, and then OK in the commit dialog box. - Then i get the described error (apache BUSY). What happened then: - "svn st" in command line gave me a lot of "L" files and directories - I issued a "svn cleanup" which solved the "L"s. - Trying the commit again from netbeans, i got the same error, but this time, after the error, no "L" appeared when i typed "svn st" in command line. - So finally i tried to commit from command line, but i got a "sqlite locked" error. - I closed netbeans, but the process remained active, so i killed it manually. - Back in command line this time the "svn ci" worked like a charm. When i turned netbeans on again, everything was fine and i could do a commit with no problem.
Just got this problem in NetBeans 7.3: svn: E200030: BUSY (error dialog says: "org.apache.subversion.javahl.ClientException: E200030: BUSY") All I did was request an svn update through NetBeans, and it's the first time I've seen the error. I did not access svn project dir concurrently by other means (e.g. native command line client). Now it happens every time I try to update the project. (Guessing it might disappear after IDE restart.) Local svn client is: svn, version 1.7.5 (r1336830)
@oyviste Perhaps this is the same as bug 229355 ?
(In reply to comment #11) > @oyviste Perhaps this is the same as bug 229355 ? Sure, it could very well be.
I first got the error checking out a project on windows 8. The project was only partially checked out. Subsequent clean/update commands failed as well, but always got me a bit more data. Eventually I used TortoiseSVN which didn't show any problem. I don't think this is a duplicate of Bug 229355 as no commit is onvoled and clean doesn't show any error.
*** This bug has been marked as a duplicate of bug 229355 ***