[jbosstools-issues] [JBoss JIRA] (JBIDE-11892) JaxRsMetaModelBuilder runs on non-JAXRS enabled projects

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-11892:
--------------------------------

    Description: 
At some point, I had severe performance issues (all cores at 100%) while importing the projects from https://github.com/hibernate/hibernate-search.
I disabled all the JBT maven configurators to try to see if this was caused by our maven integration.
I can't tell if it's related but, during import, I saw several JAX RS Metamodel build jobs running very slowly, even though none of the hibernate search projects have the jaxrs nature or builder enabled.

!JaxrsMetamodelBuildJob.png!

jstack showed me that :

{noformat}
"Worker-114" prio=6 tid=0x0000000010134800 nid=0x310 waiting on condition [0x00000000203de000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
     at java.lang.Thread.sleep(Native Method)
     at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:259)
     at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:214)
     at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:515)
     at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:584)
     at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.searchForAnnotatedTypes(JaxrsAnnotationsScanner.java:172)
     at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.findHttpMethodTypes(JaxrsAnnotationsScanner.java:148)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:182)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:122)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{noformat}

JaxrsMetamodelBuildJob doesn't seem to filter the projects elligible for JAXRS stuff.

I can't say this is the cause of the performance issues I saw (I need to do some profiling) but anyway JaxrsMetamodelBuildJob should never run for non-JAXRS enabled projects.

  was:
At some point, I had severe performance issues (all cores at 100%) while importing the projects from https://github.com/hibernate/hibernate-search.
I disabled all the JBT maven configurators to try to see if this was caused by our maven integration.
I can't tell if it's related but, during import, I saw several JAX RS Metamodel build jobs running very slowly, even though none of the hibernate search projects have the jaxrs nature or builder enabled.

jstack showed me that :

{noformat}
"Worker-114" prio=6 tid=0x0000000010134800 nid=0x310 waiting on condition [0x00000000203de000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
     at java.lang.Thread.sleep(Native Method)
     at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:259)
     at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:214)
     at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:515)
     at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:584)
     at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.searchForAnnotatedTypes(JaxrsAnnotationsScanner.java:172)
     at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.findHttpMethodTypes(JaxrsAnnotationsScanner.java:148)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:182)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:122)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75)
     at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{noformat}

JaxrsMetamodelBuildJob doesn't seem to filter the projects elligible for JAXRS stuff.

I can't say this is the cause of the performance issues I saw (I need to do some profiling) but anyway JaxrsMetamodelBuildJob should never run for non-JAXRS enabled projects.


    
> JaxRsMetaModelBuilder runs on non-JAXRS enabled projects
> --------------------------------------------------------
>
>                 Key: JBIDE-11892
>                 URL: https://issues.jboss.org/browse/JBIDE-11892
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Webservices
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Fred Bricon
>            Assignee: Xavier Coulon
>            Priority: Critical
>             Fix For: 3.3.0.CR1
>
>         Attachments: JaxrsMetamodelBuildJob.png
>
>
> At some point, I had severe performance issues (all cores at 100%) while importing the projects from https://github.com/hibernate/hibernate-search.
> I disabled all the JBT maven configurators to try to see if this was caused by our maven integration.
> I can't tell if it's related but, during import, I saw several JAX RS Metamodel build jobs running very slowly, even though none of the hibernate search projects have the jaxrs nature or builder enabled.
> !JaxrsMetamodelBuildJob.png!
> jstack showed me that :
> {noformat}
> "Worker-114" prio=6 tid=0x0000000010134800 nid=0x310 waiting on condition [0x00000000203de000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
>      at java.lang.Thread.sleep(Native Method)
>      at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:259)
>      at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:214)
>      at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:515)
>      at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:584)
>      at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.searchForAnnotatedTypes(JaxrsAnnotationsScanner.java:172)
>      at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.findHttpMethodTypes(JaxrsAnnotationsScanner.java:148)
>      at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:182)
>      at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:122)
>      at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75)
>      at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56)
>      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> JaxrsMetamodelBuildJob doesn't seem to filter the projects elligible for JAXRS stuff.
> I can't say this is the cause of the performance issues I saw (I need to do some profiling) but anyway JaxrsMetamodelBuildJob should never run for non-JAXRS enabled projects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira