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.

Bug 18997 - "Invalid lock" when switching to other project
Summary: "Invalid lock" when switching to other project
Status: CLOSED DUPLICATE of bug 18178
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: rmatous
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-03 08:53 UTC by R. Schiess
Modified: 2008-12-22 16:54 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
log (551.38 KB, text/plain)
2002-01-03 08:59 UTC, R. Schiess 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description R. Schiess 2002-01-03 08:53:38 UTC 
after the exception everything seemed to work all the same...
log to follow...
Comment 1 R. Schiess 2002-01-03 08:59:59 UTC 
Created attachment 3963 [details]
log
Comment 2 rmatous 2002-01-03 17:30:06 UTC 
Please add build number from build_info. Also steps how to reproduce
and other comments would be valuable.
Comment 3 R. Schiess 2002-01-04 07:27:54 UTC 
build is 200112102331

Just right now I again switched to another project and a similar 
error occurred:

Fri Jan 04 08:21:24 CET 2002: org.openide.filesystems.FSException:  
Invalid lock [null] for file Windows/Components/GEA_Applet #005BLMod; 
1#002E25#005D.settings in Multi-Filesystem with current lock [null].
Annotation: Cannot save settings to Windows/Components/GEA_Applet 
#005BLMod; 1#002E25#005D.settings
org.openide.filesystems.FSException: Invalid lock [null] for file 
Windows/Components/GEA_Applet #005BLMod; 1#002E25#005D.settings in 
Multi-Filesystem with current lock [null].
        at org.openide.filesystems.FSException.io(FSException.java:84)
        at org.openide.filesystems.MultiFileObject.testLock
(MultiFileObject.java:513)
        at org.openide.filesystems.MultiFileObject.getOutputStream
(MultiFileObject.java:473)
        at org.openide.filesystems.MultiFileObject.getOutputStream
(MultiFileObject.java:478)
        at org.openide.loaders.InstanceDataObject$Saver.run
(InstanceDataObject.java:1768)
        at org.openide.filesystems.EventControl.runAtomicAction
(EventControl.java:89)
        at org.openide.filesystems.FileSystem.runAtomicAction
(FileSystem.java:388)
        at org.openide.loaders.InstanceDataObject$Saver.save
(InstanceDataObject.java:1786)
        at 
org.openide.loaders.InstanceDataObject$SettingsInstance.saveInstance
(InstanceDataObject.java:1459)
        at 
org.openide.loaders.InstanceDataObject$SettingsInstance.saveInstance
(InstanceDataObject.java:1449)
        at org.openide.loaders.InstanceDataObject$SettingsInstance.run
(InstanceDataObject.java:1500)
        at org.openide.util.Task.run(Task.java:152)
[catch] at org.openide.util.RequestProcessor$ProcessorThread.run
(RequestProcessor.java:622)


I don't have any hints. I just switched the project.
I'm sorry to say that the new release is so buggy that I'm thinking 
of going back to 3.2.
Comment 4 rmatous 2002-01-07 09:03:08 UTC 
Fixed in release33 (MultiFileObject 1.89.2.3). Synchronization of
getOutputStream was slightly modified. Hopefully it will help (but not
reproducible problem).

(According to bug count should not be 3.3 worse then 3.2.)

*** This issue has been marked as a duplicate of 18178 ***
Comment 5 Quality Engineering 2003-07-01 16:03:54 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 6 Quality Engineering 2003-07-01 16:23:48 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.