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: | Transition between maven groups hangs up IDE | ||
---|---|---|---|
Product: | projects | Reporter: | mjreged <mjreged> |
Component: | Maven | Assignee: | Milan Kuchtiak <mkuchtiak> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | jskrivanek, jtulach, mkleint, mkuchtiak |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
During group switching snapshot 1
another snapshot Group is a parent Pom with 13 modules- jars, wars, ears. |
Description
mjreged
2009-04-15 00:20:31 UTC
Created attachment 80088 [details]
During group switching snapshot 1
Created attachment 80089 [details]
another snapshot
what kind of groups are these? folder-based, subproject-based or based on open projects? there's a lot of time spent in filesystem operations. If your group is folder based, can you give an estimate on the number of subfolders (recursively) in the group folder? jtulach: also Feature on Demand is involved and the project loading via FoD takes some time.. often the FS activities are triggered by FoD, please evaluate I don't think Filesystem operations can take minutes. Only if sources are on network drives. Suspicious is org.netbeans.modules.maven.jaxws.JaxWsOpenHook$WebservicesChangeListener.updateJaxWs() hotspot in the maven-switching-groups1.nps snapshot. updateJaxWs() is afaik only waiting for the CP scanning to finish (to perform it's own task). #162635 is related to that.. I am sure this is not the root cause of the problem, but please note that maven.jaxws is using request processor incorrectly. There seems to be about 20 threads blocked in updateJaxWs. Please use own dedicated RequestProcessor. Created attachment 80158 [details]
Group is a parent Pom with 13 modules- jars, wars, ears.
OK, I'll change the code to use own (dedicated) instance of RP. I Need to point out and ask; Why is netbeans wasting my CPU cycles on some JAXWS processing. My project has jaxws configured in spring configuration by CXF and there is nothing that i would want netbeans to do in this regard. When i start a new Netbeans installation it asks me about jaxws entries in web.xml, i select the option to never ask me about it again. This choice i made should be checked and jaxws processing should leave me alone. Just assuming a lot here. reassigning to mkuchtiak. "JAX-WS processing" is a listener mechanism implemented to recognize all web services - java classes annotated with @javax.jws.WebService annotation, in a Web or EJB project. It's being initialized when the project is being opened. Hopefully this will help : http://hg.netbeans.org/main?cmd=changeset;node=50b123a52883 Integrated into 'main-golden', will be available in build *200904170201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/50b123a52883 User: mkuchtiak@netbeans.org Log: #162652: created own instance of RequestProcessor for WS Annotations handling mjreged, could you please verify the fix? v. |