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: | IllegalStateException: The data object C:\Source\5.4\Applications\swCommunity\web\calendarWeek.jsp is invalid; you may not call getNodeDelegate on it any more; see #17020 and please fix your code | ||
---|---|---|---|
Product: | platform | Reporter: | trobbins <trobbins> |
Component: | Data Systems | Assignee: | Jiri Skrivanek <jskrivanek> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | ksilz |
Priority: | P3 | Keywords: | THREAD |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=149022 | ||
Issue Type: | DEFECT | Exception Reporter: | 149022 |
Attachments: |
stacktrace
stacktrace |
Description
trobbins
2009-04-06 17:26:01 UTC
Created attachment 79549 [details]
stacktrace
Build: NetBeans IDE Dev (Build 200904011705) VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03 OS: Windows XP, 5.1, x86 User Comments: Deleted plug-in folder in Grails project after upgrading to Grails 1.1. Stacktrace: java.lang.IllegalStateException: The data object D:\source\NetBeansProjects\SeldonManager2\plugins\grails-dynamic-jasper-0.2.zip is invalid; you may not call getNodeDelegate on it any more; see #17020 and please fix your code at org.openide.loaders.DataObject.getNodeDelegate(DataObject.java:270) at org.openide.loaders.DataObject.getClonedNodeDelegate(DataObject.java:306) at org.openide.loaders.FolderChildren.createNodes(FolderChildren.java:207) at org.openide.loaders.FolderChildren.createNodes(FolderChildren.java:66) at org.openide.nodes.Children$Keys$KE.nodes(Children.java:1608) at org.openide.nodes.EntrySupport$Lazy$EntryInfo.getNode(EntrySupport.java:1554) Created attachment 79573 [details]
stacktrace
Not sure what can we do with this. DataObject is valid in FolderChildren.createNodes but probably some other thread make it invalid before it comes to DataObject.getNodeDelegate. Further synchronization is probably risky. *** This issue has been marked as a duplicate of 153008 *** |