Bugzilla – Full Text Bug Listing
| Summary: | Its back: Core Exception [code 380] The resource tree is locked for modifications | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
| Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | kai-uwe_maetzel |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 M5 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Dani Megert
Ah: steps to reproduce: 1. started workspace 2. imported binary plug-ins 3. rebuild all don't know at which stage it happened. Weird, duplicate of bug 29585. We have released a workaround to protect against platform bug/limitation (cannot run operation while resource tree is locked). Need to investigate again. Also, Jerome you should improve the logged exception trace so that we see what actually went wrong. note that the first problem was with setting JRE lib. We now switched and use JRE container. Was able to reproduce: You need to save the workspace with only the resource perspective open to see the problem. Workaround is to open the Java perspective first before doing the plugin import. Improved logging to log nested exception instead of JavaModelException. The
real stack trace is:
org.eclipse.core.internal.resources.ResourceException: The resource tree is
locked for modifications.
at org.eclipse.core.internal.resources.Workspace.beginOperation
(Workspace.java:137)
at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1579)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:2607)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer
(JavaCore.java:2713)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize
(JREContainerInitializer.java:54)
at org.eclipse.jdt.core.JavaCore$1.run(JavaCore.java:857)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:852)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer
(JavaCore.java:852)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1428)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1344)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1320)
at org.eclipse.jdt.internal.core.DeltaProcessor.addDependentProjects
(DeltaProcessor.java:202)
at org.eclipse.jdt.internal.core.DeltaProcessor.deleting
(DeltaProcessor.java:723)
at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged
(DeltaProcessor.java:1590)
at org.eclipse.core.internal.events.NotificationManager$1.run
(NotificationManager.java:137)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:852)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.core.internal.events.NotificationManager.notify
(NotificationManager.java:152)
at org.eclipse.core.internal.events.NotificationManager.handleEvent
(NotificationManager.java:124)
at org.eclipse.core.internal.resources.Workspace.broadcastEvent
(Workspace.java:163)
at org.eclipse.core.internal.resources.Resource.delete
(Resource.java:602)
at org.eclipse.core.internal.resources.Project.delete(Project.java:292)
at
org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.createProject
(PluginImportOperation.java:151)
at org.eclipse.pde.internal.ui.wizards.imports.PluginImportOperation.run
(PluginImportOperation.java:119)
at org.eclipse.core.internal.resources.Workspace.run
(Workspace.java:1580)
at org.eclipse.pde.internal.ui.wizards.imports.PluginImportWizard$2.run
(PluginImportWizard.java:152)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run
(ModalContext.java:95)
Tree was not marked as locked by DeltaProcessor during PRE_DELETE, thus the workaround could not work in this case. Fixed *** Bug 30465 has been marked as a duplicate of this bug. *** Verified. |