[
https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi...
]
Daniel Atallah commented on JBIDE-22578:
----------------------------------------
Sorry for the delayed response, I was out of the office for a few weeks.
[~mmalina], your steps for the dynamic web project seem reasonable to me, and looks very
similar to what we have.
One difference (which probably isn't important) is that for the "Temporary deploy
folder", we have the default {{"standalone\tmp"}} value instead of a full
path.
Another difference is that there are 20 or so java sub-module projects.
As I mentioned earlier, this behavior doesn't happen with every publish - we can
recreate it reliably by making a number of changes that cause incremental publications
over a few minutes, but we haven't been able to identify a specific activity that
causes the behavior.
I don't think we're going to be able to come up with a simplified sample project
that works differently than what you've already created.
Would it be reasonable to add even more debugging (perhaps even to a unreleased test
build) that we can use to provide a log with the right details to track this down?
Publishing sometimes recursively deletes parent to deploy directory
-------------------------------------------------------------------
Key: JBIDE-22578
URL:
https://issues.jboss.org/browse/JBIDE-22578
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.Final
Environment: Eclipse Mars.2 Release (4.5.2)
Java 1.8.0_91
Windows 7 64-bit
JBoss EAP 6.4.0
Reporter: Daniel Atallah
Assignee: Rob Stryker
Fix For: 4.4.1.AM3
Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml
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:
{noformat}
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
{noformat}
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:
{noformat}
!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.
{noformat}
Any idea what might be happening?
Is there some debug logging we can enable to get better visibility to what's going
on?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)