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.
Thu Aug 02 07:34:31 CEST 2001: java.util.ConcurrentModificationException: Posted StackTrace Annotation: Exception occurred in Request Processor org.openide.util.RequestProcessor$Holder: Posted StackTrace(task org.openide.loaders.InstanceDataObject$SettingsInstance@7d8769 [-54280, 1, -1]) at org.openide.util.RequestProcessor$Task.createHolder(RequestProcessor.java:322) at org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:346) at org.openide.loaders.InstanceDataObject$SettingsInstance.propertyChange(InstanceDataObject.java:1159) at org.openide.util.WeakListener$PropertyChange.propertyChange(WeakListener.java:311) at org.openide.filesystems.FileSystem.firePropertyChange(FileSystem.java:542) at org.openide.filesystems.FileSystem.setValid(FileSystem.java:103) at org.openide.filesystems.Repository.addFileSystem(Repository.java:160) at org.netbeans.core.AutomountSupport.cycleFileSystems(AutomountSupport.java:279) at org.netbeans.core.AutomountSupport.updateFileSystems(AutomountSupport.java:242) at org.netbeans.core.AutomountSupport.taskFinished(AutomountSupport.java:118) at org.openide.util.Task.notifyFinished(Task.java:123) at org.openide.loaders.FolderInstance.defaultProcessObjects(FolderInstance.java:496) at org.openide.loaders.FolderInstance.access$200(FolderInstance.java:45) at org.openide.loaders.FolderInstance$2.run(FolderInstance.java:438) at org.openide.util.Task.run(Task.java:152) [catch] at org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:611) Thu Aug 02 07:34:31 CEST 2001: java.util.ConcurrentModificationException: null java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.next(HashMap.java:736) at org.netbeans.modules.javacvs.caching.JavaCvsCache.writeAllToDisk(JavaCvsCache.java:184) at org.netbeans.modules.javacvs.caching.CvsFsCache.saveToDisk(CvsFsCache.java:439) at org.netbeans.modules.cvsclient.NbJavaCvsFileSystem.writeObject(NbJavaCvsFileSystem.java:348) at java.lang.reflect.Method.invoke(Native Method) at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864) at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366) at org.openide.loaders.XMLSettingsSupport.storeSerialData(XMLSettingsSupport.java:117) at org.openide.loaders.XMLSettingsSupport.storeToXML10(XMLSettingsSupport.java:82) at org.openide.loaders.InstanceDataObject$SettingsInstance.saveInstance(InstanceDataObject.java:1123) at org.openide.loaders.InstanceDataObject$SettingsInstance.run(InstanceDataObject.java:1138) at org.openide.util.Task.run(Task.java:152) [catch] at org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:611)
Happened to me during the new way of storing filesystems settings to disk. I tried to start with a project from release32 with a bunch of javacvs filesystems and sometimes this exception occurs. I'll check my changes into the trunk today (I have to fix q-build issues), but I would approciate you to check what is wrong, cause it seems at least serialization of your filesystem is broken.
I guess I'll have to add some synchronized blocks into the cache code. (a thing I didn't want to do). I guess this issue is related to the issue 12879: http://javacvs.netbeans.org/issues/show_bug.cgi?id=12879
i've added the synchronized identifier to the methods that read/write to the cache and also to methods that read the local dir structure.. hopefully this will fix the problem.
I tried to reproduce this concurrent modification exception in request processor without any success so I assume it got fixed. I had 11 moun- ted CVS filesystems using Built-in Client and did several restarts of the IDE. Verified in development build of NetBeans 3.3 #200110220100.
*** Issue 18538 has been marked as a duplicate of this issue. ***
Target milestone was changed from not determined to TBD
Changing Target Milestone to 3.3 according to the verification comment from Jiri.
Resolved for 3.4.x or earlier, no new info since then -> closing.