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 119293 - [60cat] File Locked Exception while initiating the attachment process
Summary: [60cat] File Locked Exception while initiating the attachment process
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 00:13 UTC by wobster
Modified: 2007-10-25 20:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wobster 2007-10-18 00:13:47 UTC
While I was initiating the attachment of the profiler to an existing process, I got this exception:
http://statistics.netbeans.org/exceptions/detail.do?id=8204
Comment 1 J Bachorik 2007-10-19 08:00:23 UTC
according to the exception description from http://statistics.netbeans.org/exceptions/detail.do?id=8204 this issue
belongs to openide/filesystems component
reassigning
Comment 2 rmatous 2007-10-19 12:53:33 UTC
Seems like common problem: cannot read from InputStream because OutputStream is in use or just not closed.

See user comments:
Trying to attach the profiler to a running debug session. Before I started, I added two inclusive filters and switched
from profile part of the application to run whole application.
Comment 3 Jiri Sedlacek 2007-10-22 14:22:11 UTC
I'm not able to reproduce on similar configuration. Do you have some reliable steps always/often causing this exception
to be thrown? It would help a lot with finding the cause. Also, if you will be able to reproduce again, could you please
attach the IDE logfile?

Lowering priority, the problem should be harmless.
Comment 4 Jiri Sedlacek 2007-10-25 20:33:48 UTC
Based on the stacktrace the exception comes from other part of the IDE, not from the profiler. I've done the best I can
on profiler side, the configurations.xml file is now accessed in AtomicAction which prevents possible listeners to get
any notifications about filesystem changes when (== during) accessing the file.

If you reproduce the problem again, please provide as much information about the conditions as possible and attach the
IDE logfile.

Should be fixed in trunk.


/cvs/profiler/modules/main/src/org/netbeans/modules/profiler/ui/stp/ProfilingSettingsManager.java,v  <-- 
ProfilingSettingsManager.java
new revision: 1.2; previous revision: 1.1