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.
Build: NetBeans IDE Dev (Build 200909151512) VM: Java HotSpot(TM) 64-Bit Server VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Linux, 2.6.28-15-generic, amd64 User comments: right click on maven webapp Maximum slowness yet reported was 7691 ms, average is 5816
This is coming from org.netbeans.modules.maven.j2ee.J2eeRecoPrivTemplates.getRecommendedTypes, and was introduced by fix for issue 170537. This is calling WebModule.getJ2eeProfile, which is slow. The question is - is this method supposed to be fast? Or should it not be called in AWT? That's a question for Petr H.
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=158199
I run into this problem many times every day. Whenever I want to run or debug a maven webapp, close a webapp, update from subversion I have to wait (sometimes for 30s or more). I don't submit all of the slowness reports because if I submit the report I have to wait again when I right click on the project. It would be great if a fix for this could make it into 6.8.
Added 68cat prefix as this is affecting my use of NB68 dev in the netcat program.
Petre H. can you please evaluate?
At least some reports (http://statistics.netbeans.org/exceptions/exception.do?id=293782) are triggered by WebActionProvider.isActionEnabled which may parse web.xml (IO in EDT). I'll evaluate couple of others.
Reports coming from maven are caused by xml parsing in method WebModuleImpl.getJ2eeProfile(). This is not really new method the whole body is the same as it was in previous release (method getJ2eePlatformVersion()). So I'm not sure how this method was originally designed - whether intended to be fast or not. I would suppose this (or similar method) is called at many places so these should be implemented to not to do file parsing. I'll try to find out some details on methods usage.
Cc'ing Denis, I believe he was looking into similar reports before.
6.8 RC1 is not having this problem now. But now opening project takes forever and causes netbeans to hang. OS:2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686 i686 i386 GNU/Linux JDK: java version "1.6.0_12" Java(TM) SE Runtime Environment (build 1.6.0_12-b04) Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode, sharing) Thanks, Pawan Kumar
>This is calling WebModule.getJ2eeProfile it delegates call to ProjectWebModule.getJ2eeProfile() . I don't see in its implementation any time consuming problems. It just retrieves property without any additional computation/initialization. >At least some reports triggered by WebActionProvider.isActionEnabled which may >parse web.xml I see some pointers to isActionEnabled() for some actions but it seems these actions are related to project xml configuration files. Because I don't see any mention of various Web models which should be used for accessing to info like web.xml. We have had problems with performance when Web models was used ( I already mentioned these models ). There are number of decisions was done for avoiding these problems. I don't see any mentions of usages such models ( I just red the bug description without deep reports details ). If you find stack trace with j2ee ( web ) model usages which could relate to this bug please write it here. I will help to analyze them respectively performance.
Created attachment 92147 [details] nps snapshot Was right clicking on the maven project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974 No response to the right click at all. I am still trying to figure out what is going on.
Created attachment 92148 [details] nps snapshot Was right clicking on the maven project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974 No response to the right click at all. I am still trying to figure out what is going on.
Created attachment 92149 [details] nps snapshot Was right clicking on the maven project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974 No response to the right click at all. I am still trying to figure out what is going on.
Created attachment 92150 [details] nps snapshot Was right clicking on the maven project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974 No response to the right click at all. I am still trying to figure out what is going on.
Created attachment 92153 [details] nps snapshot Just right clicking on a project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974. The context menu did not pop up for even 30 seconds befor this. Repeatable, no other tasks.
Created attachment 92154 [details] nps snapshot Just right clicking on a project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974. The context menu did not pop up for even 30 seconds befor this. Repeatable, no other tasks.
Created attachment 92155 [details] nps snapshot Just right clicking on a project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974. The context menu did not pop up for even 30 seconds befor this. Repeatable, no other tasks.
Created attachment 92156 [details] nps snapshot Just right clicking on a project as reported in https://netbeans.org/bugzilla/show_bug.cgi?id=177974. The context menu did not pop up for even 30 seconds befor this. Repeatable, no other tasks.
Created attachment 92927 [details] nps snapshot
Created attachment 93183 [details] nps snapshot After activating the virtual private network, which means that netbeans has no longer connection to the internet, I push the right mouse button on a maven web projekt, to open the menue. Then the ide hangs for more than one minute until timeout occurs.
Changing the default owner to issues@javaee.
*** Bug 177974 has been marked as a duplicate of this bug. ***
Are there any chances of getting this resolved?
Looking at the duplicate slowness reports, all of them are coming from NB 6.8 or pre-6.8 builds - there is no report from 6.9 dev builds. Can anyone confirm whether this is still happening in 6.9 dev? Could this be fixed in 6.9 builds? If this is still reproducible, then it would be great to have slowness reports from the current builds.
Not able to reproduce now -> FIXED.