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 246466 - rename class refactoring takes 60+seconds before classpath scanning dialog goes away
Summary: rename class refactoring takes 60+seconds before classpath scanning dialog go...
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.0
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-14 19:17 UTC by emiddio
Modified: 2015-04-17 07:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
profiling snapshot (1.11 MB, application/octet-stream)
2014-08-14 19:19 UTC, emiddio
Details
messages log file (113.10 KB, text/plain)
2014-08-19 18:09 UTC, emiddio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description emiddio 2014-08-14 19:17:49 UTC

    
Comment 1 emiddio 2014-08-14 19:18:19 UTC
rename class refactoring takes 60+seconds before classpath scanning dialog goes away

i am attaching a profiling dump during a couple of rename refactorings.
Comment 2 emiddio 2014-08-14 19:19:07 UTC
Created attachment 148709 [details]
profiling snapshot
Comment 3 Jiri Kovalsky 2014-08-18 08:45:35 UTC
Hello Gary, can you please give us more information? How big is your JavaEE project (how many classes, how many libraries, is it stored locally or on network)? How many GBs is your PC's memory? Any other demanding applications/processes running together with NetBeans?
Comment 4 Tomas Hurka 2014-08-18 15:02:26 UTC
Please also attach messages.log file. Thanks.
Comment 5 emiddio 2014-08-18 15:20:01 UTC
If you need exact number of classes, and jar files I will have to provide later.
Its a java project - not java EE. The files are all checked out from cvs. I added many jars - approx 100, have about 622+/- java files.

I also use visualvm and jmc to try and understand the hold up - even began looking at some netbeans sources - but nothing got figured out yet.

My environment is pc laptop - 8core Intel ? 16GB ram, 500 GByte drive. In this case I closed the other projects so only 1 project was open to try and help.

NB is configured to not do scanning in the file options dialog. And this is NOT a Compile on Save project.

Nothing was happening on the machine except netbeans consuming CPU - other than when I was attached to NB with visualvm. Most of time when waiting on netbeans the task manager would show what looked like 1 core maxed out of cpu usage. And visualvm seemed to indicate prob just 1 thread consuming the cpu. Also the disk light was mostly OFF - no particular disk activity that I could tell.

64bit jvm 1.8.0_05 i think.
Comment 6 Jiri Kovalsky 2014-08-19 04:50:03 UTC
Thanks Gary, and the messages.log?
Comment 7 emiddio 2014-08-19 18:09:25 UTC
Created attachment 148775 [details]
messages log file
Comment 8 Tomas Hurka 2014-08-26 15:01:15 UTC
Thanks for the messages.log file. It is interesting that you said that this is not Java EE projects, since the self-sampler snapshot shows that most of the time in "Editor Parsing Loop" thread is spent in org.netbeans.modules.j2ee.metadata.model.api.support.annotation.PersistentObjectManager.typesChanged(). This is clearly J2EE related thing. Are you sure that your project does not contain any j2ee related artefacts?
Comment 9 emiddio 2014-08-26 15:58:20 UTC
The project was created as a java project. I then copy sources to the project. And add jars to the project. I compile the project and can run the project where I select some main class. But mostly just use the project as a mechanism for editing code, refactoring, and doing test compilations before moving code to actual machine - Solaris 11 - where is again rebuilt and deployed.

But yes - when actually deployed on Solaris 11 it is deployed into OC4J - Oracle Containers for Java - and runs as a java ee deployed EAR - using JMS, Database, and EJB's with lots of JPA1 annotations.

My single netbeans project includes all the sources for around 17 different builds which when they get deployed and run on the Solaris 11 run in around 17 JVM's - only 1 is Java EE deployed to OC4J- others are stand alone java that make use of remote EJB imvocation and JMS.
Comment 10 Tomas Hurka 2014-08-27 08:46:20 UTC
Most of the time in "Editor Parsing Loop" is spent in org.netbeans.modules.j2ee.metadata.model.api.support.annotation.PersistentObjectManager.typesChanged() - reassigning to j2ee for further evaluation.
Comment 11 Petr Hejl 2015-04-17 07:17:28 UTC
Unfortunately this looks like slow filesystem (under heavy load?). I went through the snapshots - there are various waits (60s, 5s, 5s...) all of them spending time in java.io.WinNTFileSystem.list[native]().