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: | NetBeans hangs | ||
---|---|---|---|
Product: | obsolete | Reporter: | vieiro <vieiro> |
Component: | Facelets 1.1.x | Assignee: | Petr Pisl <ppisl> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Thread dump (kill -3 of the JVM). Note AWT thread hung.
messages.log (excerpt) |
Description
vieiro
2007-09-06 13:04:45 UTC
Created attachment 48255 [details]
Thread dump (kill -3 of the JVM). Note AWT thread hung.
Created attachment 48256 [details]
messages.log (excerpt)
the threadlock is caused by the facelets support org.netbeans.modules.web.frameworks.facelets.editor.FaceletsContextInfoImpl.getJSPColoringData(FaceletsContextInfoImpl.java:67) causing that a document writelock is requested under document's readlock. There has already been such report, reassigning to owner of the module for further resolution. BTW, the module is no longer in netbeans 6.0, the workaround is to disable the facelets support module. Upps. Sorry by that!! So I assume it can be closed now? Thanks indeed, Antonio I am reassigning to facelets module, Petr Pisl (who is the owner of Facelets) can verify and close next week when he comes from vacation. I'm going to fix it asap. I will provide new version of the Fecelets support module for NetBeans 5.5 and 5.5.1. Version for NetBeans 6.0 should be available soon. This is duplication of issue #110082. I attached there a jar file with possible fix. You can try it and let me know, whether it helps. Thanks *** This issue has been marked as a duplicate of 110082 *** |