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 10446 - .xmlinfo parser IOException after mount & unmount JAR
Summary: .xmlinfo parser IOException after mount & unmount JAR
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: _ pkuzel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-18 07:50 UTC by Jesse Glick
Modified: 2008-12-22 19:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IOException printed on console (1.13 KB, text/plain)
2001-03-18 07:51 UTC, Jesse Glick 		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 Jesse Glick 2001-03-18 07:50:38 UTC 
[release32 mar 16] I mounted ant.jar and ant-optional.jar in Filesystems and
updated the parser database on them. Then I unmounted them again. Noticed many
exceptions like the attached one on console (netbeans.debug.exceptions=true).
Looks like XMLDataObject should be more careful about parsing things in the
background--check if they still really exist first.
Comment 1 Jesse Glick 2001-03-18 07:51:33 UTC 
Created attachment 823 [details]
IOException printed on console
Comment 2 _ pkuzel 2001-03-19 17:40:44 UTC 
Strange enough. All XMLDataObject should be dead at that time. However it is no
problem to add a check I am going to investigate why the parser is still alive.
Comment 3 _ pkuzel 2001-03-29 15:52:23 UTC 
I do not lock files on reading/parsing.
So if someone deletes the parsed file meanwhile it may occure.
No check will prevent the exception to occure.

The printed exception is just infomational.
Comment 4 Quality Engineering 2003-07-01 15:52:57 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 5 Quality Engineering 2003-07-01 16:12:08 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.