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.

Bug 204035 - Nobody listens on config/Modules on 2nd start
Summary: Nobody listens on config/Modules on 2nd start
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 6.x
Hardware: All All
: P2 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-20 19:06 UTC by Tomas Hurka
Modified: 2011-12-12 16:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Hurka 2011-10-20 19:06:18 UTC 
This is reproduced only with VisualVM, not with netbeans. See original VisualVM bug #454 <http://java.net/jira/browse/VISUALVM-454>


Kill Application plugin installs fine in the 1st VisualVM session but in subsequent sessions installation timeouts.

Steps to reproduce:
===================
1. Launch VisualVM with empty userdir.
2. Invoke "Tools > Plugins", switch to "Available Plugins" tab, check "KillApplication" entry and push "Install" button.
3. Push "Next >", confirm license and finish the installation. It will be successful.
4. Now delete the userdir e.g. ~/.visualvm/1.3.2 and launch VisualVM.
5. Exit it and launch again.
6. Repeat steps 2 and 3 but installation will timeout.
Comment 1 Tomas Hurka 2011-10-20 19:26:45 UTC 
The log from the autoupdate shows that the plugin installs fine, but according to  org.netbeans.core.startup.ModuleList log, the filesystems never fires the 'fileDataCreated' event that there is a new .xml file in the Modules directory. While debugging the code, I found out that ModuleList listens on the fileobject representing the Modules directory, but no-one asked it for its children and therefor it fires no events. Based on this evaluation I was able to workaround this problem, but simply invoking getChildren() on the Modules directory fileobject in module install of one of the VisualVM modules. See <http://java.net/projects/visualvm/sources/svn/diff/trunk/visualvm/appui/src/com/sun/tools/visualvm/modules/appui/Install.java?rev1=2983&rev2=2984>.
Comment 2 Jaroslav Tulach 2011-10-31 09:55:22 UTC 
Thanks for the analysis: ergonomics#14528d224a90
Comment 3 Quality Engineering 2011-11-01 15:10:12 UTC 
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/14528d224a90
User: Jaroslav Tulach <jtulach@netbeans.org>
Log: #204035: Initialize the listener by always asking for children
Comment 4 Tomas Hurka 2011-12-12 16:55:06 UTC 
Verified in VisualVM with NB 7.1 RC2.