[
https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi...
]
Rastislav Wagner commented on JBIDE-17696:
------------------------------------------
With -consoleLog -debug /path/to/the/.option I'm getting exception when updating maven
configuration
{code}
org.eclipse.core.runtime.AssertionFailedException: assertion failed: ThreadJob(Updating
Maven Project(1602),[MultiRule[R/],R/,R/]) conflicts and ran simultaneously with Updating
Maven Project(1602)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.internal.jobs.JobManager.yieldRule(JobManager.java:1452)
at org.eclipse.core.internal.jobs.InternalJob.yieldRule(InternalJob.java:603)
at org.eclipse.core.runtime.jobs.Job.yieldRule(Job.java:760)
at
org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.waitForAllUpdates(DependencyGraphImpl.java:691)
at
org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.getReferencingComponents(DependencyGraphImpl.java:126)
at
org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.getReferencingComponents(DependencyGraphImpl.java:116)
at
org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferencingComponents(VirtualComponent.java:579)
at
org.eclipse.jst.j2ee.project.EarUtilities.getReferencingEARProjects(EarUtilities.java:274)
at
org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:370)
at
org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
at
org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
at
org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
at
org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
at
org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
at
org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:118)
at
org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
at
org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
at
org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:747)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:876)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:291)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.clean(MavenBuilder.java:211)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:736)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:401)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:114)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:435)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
at
org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
I was able to reproduce the issue using automated UI tests (I tried manually but I was not
able to do so due to exception mentioned above).
Output i got:
{code}
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) will yieldRule to
ThreadJob(null,[P/testWEB_JPA_noRuntime])
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) will yieldRule to
ThreadJob(null,[P/testWEB_JPA_noRuntime])
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) is waiting for
ThreadJob(null,[P/testWEB_JPA_noRuntime]) to transition from WAITING state
{code}
If this is not enough, I can try manually again, but it might take some time.
Enabling Maven Dependency Management job waits forever
------------------------------------------------------
Key: JBIDE-17696
URL:
https://issues.jboss.org/browse/JBIDE-17696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.2.0.Beta2
Environment: OpenJDK 1.7, 64b
Ubuntu 12.04, 64b
Reporter: Rastislav Wagner
Fix For: 4.2.x
Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png,
wait1.png, wait2.png
I dont have exact steps to reproduce because this usually occurs after longer work.
I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
1. Create Dynamic Web Project
2. Convert to maven project (using Configure -> Convert to maven..)
3. Add some dependency
4. check if proper facet was enabled
5. delete project and repeat
After trying this 10-15 times (sometimes more, sometimes less), during step 2
"Enabling Maven Dependency Management" job is waiting and never ends - see
screenshot - there's always "Setting classpath containers".
JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)