[
https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22605:
-------------------------------------
We should clearly separate out the two issues.
For the deployment marker, it seems there may be a case where we forget to add the
.dodeploy marker. This case needs to be discovered and isolated if possible. I am unable
to replicate it.
For the second issue, re: server stop: I am 100% unable to replicate. How often is this
replicatable for you? Does it happen once a session? Once a startup? Etc?
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.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)