-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
4.3.1.Final
-
None
-
devex #129 March 2017
-
5
-
For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it.
It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools.
We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
Our workspaces are structured as follows:
WORKSPACEROOT=$DEVROOT\workspacename # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server $WORKSPACEROOT\deploy # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling $WORKSPACEROOT\src # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments $WORKSPACEROOT/server/data # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments $WORKSPACEROOT/server/tmp
The Server is configured to "Automatically publish when resources change".
What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT.
The eclipse log includes the following:
!ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 !MESSAGE Problems occurred refreshing resources !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 !MESSAGE Problem finding next change, code: 5 !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 !MESSAGE Incremental publish failed for module $MODULENAME !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
Any idea what might be happening?
Is there some debug logging we can enable to get better visibility to what's going on?
