[
https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi...
]
Daniel Atallah commented on JBIDE-22578:
----------------------------------------
Fortunately, I have the stdout and stderr logs too from when the above output was created
(unfortunately, there doesn't appear to be anything useful).
stdout:
{noformat}
Install location:
file:/c:/lean/development/eclipse-jee-mars-R-64/
Configuration file:
file:/c:/lean/development/eclipse-jee-mars-R-64/configuration/config.ini loaded
Configuration location:
file:/c:/lean/development/eclipse-jee-mars-R-64/configuration/
Framework located:
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi_3.10.100.v20150529-1857.jar
Loading extension:
reference:file:org.eclipse.osgi.compatibility.state_1.0.100.v20150402-1551.jar
eclipse.properties not found
Framework classpath:
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi_3.10.100.v20150529-1857.jar
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/
file:/c:/lean/development/eclipse-jee-mars-R-64/plugins/org.eclipse.osgi.compatibility.state_1.0.100.v20150402-1551.jar
Splash location:
c:\lean\development\eclipse-jee-mars-R-64\\plugins\org.eclipse.platform_4.5.0.v20150603-2000\splash.bmp
Debug options:
file:/C:/lean/development/eclipse-jee-mars-R-64/.options loaded
Time to load bundles: 8
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle
was activated before the state location was initialized. Will retry after the state
location is initialized.
Starting application: 1365
org.eclipse.m2e.logback.configuration: Logback config file:
C:\lean\development\tms\bilbo\src\.metadata\.plugins\org.eclipse.m2e.logback.configuration\logback.1.6.0.20150526-2032.xml
org.eclipse.m2e.logback.configuration: Initializing logback
Application Started: 15597
org.jboss.ide.eclipse.as.core /finest 15/06/16 17:29.30.117 Verifying server structure
org.jboss.ide.eclipse.as.core /finest 15/06/16 17:29.30.118 Verifying jdk is available if
server requires jdk
org.jboss.ide.eclipse.as.core /finer 15/06/16 17:29.31.278 Checking if a server is already
started: Web Poller did not find a running server at url
http://localhost:8080
{noformat}
stderr:
{noformat}
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[bundleresource://909.fwk66515916:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[bundleresource://909.fwk66515916:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See
http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type
[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
java.io.IOException: Cannot run program "C:\Program
Files\Java\jdk1.8.0_91\jre\bin\jps": CreateProcess error=2, The system cannot find
the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:485)
at
org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102)
at
org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
at
org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file
specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
at java.lang.ProcessImpl.start(ProcessImpl.java:137)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 6 more
Jun 15, 2016 5:29:38 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.1.Final
Jun 15, 2016 5:29:38 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.1.Final
Jun 15, 2016 5:29:38 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.9.Final
{noformat}
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
Priority: Blocker
Fix For: 4.4.1.S116
Attachments: jboss_deployment.jpg, 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)