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: | [67cat] [tools] JavaEE Bundle takes excessive time to activate | ||
---|---|---|---|
Product: | javaee | Reporter: | esmithbss <esmithbss> |
Component: | Code | Assignee: | issues@javaee <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | pjiricka, vkraemer |
Priority: | P3 | Keywords: | ERGONOMICS, PERFORMANCE, RANDOM |
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
esmithbss
2009-04-09 23:24:38 UTC
Have waited about 5 minute to 10 minutes now for process. Appears to definitely be hung. Unable to kill NetBeans except for issuing a SIGKILL to the actual Java process from the command line. If I manually enable JavaEE (again from a clean userdir), all of the necessary modules appear to be activated properly. Are you saying that when you... 1. start the 200904091401 build with a fresh install and a clean userdir (including the v2.1 and v3 Prelude servers) and NOT importing settings from 6.5 2. Open the Services explorer window 3. Select the Java EE Usage... item from the right-click menu on the Node labeled Servers ... there is a long pause as modules to support Ruby development are loaded. I just tried to replicate that on a recently built pull from the trunk, but could not. I did see a pause when I replaced 'Java EE usage...' with 'Ruby usage...' in step three, but it was not catastrophic. If you encounter this issue again, please try to generate a thread dump (SIGQUIT, I think) before you kill the process. Attach that thread dump to the issue. It will make the analysis of this issue a lot easier. I also can not reproduce now, I assume it was fixed by now. Please reopen if you still encounter this problem. Thanks. |