]
Rob Stryker commented on JBIDE-22605:
-------------------------------------
There is no problem with a .undeployed marker sitting there. That is fine and expected
under most cases. The .undeployed marker also shouldn't intefere with shutdown at
all.
The other issue seems to be we don't add the .dodeploy all the time (?), but my tests
seem to show we do. I'll keep invetigating.
Remote server with fs operations sometimes cannot be stopped
------------------------------------------------------------
Key: JBIDE-22605
URL:
https://issues.jboss.org/browse/JBIDE-22605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Yesterday when we were found out that remote servers don't work with management
operations (JBIDE-22601) I wanted to check if at least FS operations work.
In one instance of Eclipse, stopping such server didn't work.
But then I tried in devstudio and it worked, so I assumed it was some glitch.
But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the
one that contains a fix to the above mentioned JIRA.
From several attempts, it seems that this is only reproducible if you deploy a project.
If you just start the server and then stop, it will stop just fine.
One more thing, regardless of whether a given server can be stopped or not, I always get
this in the Error Log view during server startup:
{code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss
EAP 7.0 marvin{code}
(Let me know if you want an additional JIRA for that.)