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: | Launching HTTP monitor causes deadlock | ||
---|---|---|---|
Product: | javaee | Reporter: | Ana.von Klopp <avk> |
Component: | HTTP Monitor | Assignee: | Ana.von Klopp <avk> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P3 | Keywords: | THREAD |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Code changes |
Description
Ana.von Klopp
2003-08-26 17:04:30 UTC
Radim had added a comment to the bugtraq entry but it appears to have been cut from the report. The problem is that the initialization of a Swing component cannot be run in non-AWT thread as described in http://java.sun. com/docs/books/tutorial/uiswing/overview/threads.html. The code in question has actually already been changed for the multi-language release (I replaced the openide.awt. splitpanel with the Swing split panel) and rewrote some of the code in the process. I will review all the code in the monitor to make sure that this does not happen there or anywhere else. Leave as P3 since this bug only happens very intermittently (we have not had another report). *** Issue 38236 has been marked as a duplicate of this issue. *** See entry in duplicate for error msg. It appears that Petr fixed this one when he implemented the deployment on Tomcat 5. Thanks! Ana Created attachment 12700 [details]
Code changes
|