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.
NB 4.2 (200507181000) JDK 1.5.0_04 I've got a stream of exceptions on the console after compiling project with antscript. steps to reproduce: 1) download jEdit sources 2) create new project with existing ant script in the jEdit directory -> the field will be filled in automaticaly 3) build the project -> some warnig about deprecated methods will show up 4) browse the project in the files view (specialy the folders which contains java files) -> a very long stream of java.lang.Exception: rollback!!! appears on the console java.lang.Exception: rollback!!! at org.netbeans.modules.javacore.ExclusiveMutex.leave(ExclusiveMutex.jav a:336) at org.netbeans.mdr.NBMDRepositoryImpl.endTrans(NBMDRepositoryImpl.java: 248) Before compiling i've not come across this exceptions. I don't know if it's relevant but the class files are stored in the folders where are java files located.
Created attachment 23147 [details] exception
Please attach the whole messages.log.
Created attachment 23148 [details] log
Thanks. Looks like a problem in clazz module. Dan, please look at it.
I was able to reproduce it, but I didn't see any incorrect behaviour. Exceptions in log are only *informational* and are not written to console in release. Lowering priority to P4 as no problem in IDE behaviour was found.
I have the same problem but mine appears upon loading the IDE.
this is a serious issue, it causes IDE to flash and take control of PC while it loops through ever with these rollback issues... it makes netbeans unusable, it happens every single time I open!!!!!
joe200k: rollbacks -> it is just recovery from previous error. The real cause is that some exception is thrown before the rollback. Please file separate issue, describe steps to reproduce and attach your messages log as an attachment. Thanks.
Exception comes from mdr modules -> should be fixed by the new infrastructure
if haven't seen this exception for a long time -> v.