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.
Summary: | Race Condition in DataObjectPool.Validator.removeInvalidObject | ||
---|---|---|---|
Product: | platform | Reporter: | _ gfink <gfink> |
Component: | Data Systems | Assignee: | phamernik <phamernik> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | rkubacki, sgleason |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows 3.1/NT | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | stacktrace of blocked Automount thread |
Description
_ gfink
2001-05-11 23:31:58 UTC
Reassign to proper address. Reassign to Vita Moving to data systems Target milestone -> 3.3.1. Reassigning to the new cutodian of Data Systems. Fixed in release33 (DataObjectPool.Validator: 1.53.8.1). I found problem in validator: there is optimization that should merge requests for revalidating. But once revalidated DataObject should not be part of merge and revalidated again and again. George please can you verify fix of this issue? Thanks. Really we can remove the delay. We still can't call Repository.removeFileSystem directly from DataObject.dispose(). The mounting is blocked in that case (see atached stack trace). Is that OK? Created attachment 4429 [details]
stacktrace of blocked Automount thread
seems fine Resolved for 3.4.x or earlier, no new info since then -> closing. |