[
https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22605:
---------------------------------------
For the first several attempts, deployment worked fine. But now when I deploy the project,
strange thing happens:
It will say:
{code}11:56:06,843 INFO [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) WFLYDS0004: Found jboss-as-kitchensink-html5-mobile.war in
deployment directory. To trigger deployment create a file called
jboss-as-kitchensink-html5-mobile.war.dodeploy
{code}
And nothing more.
And on the server in the deployments directory, there is this:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.undeployed
{code}
When just before the publish, there was nothing at all.
If I undeploy in the Servers view, the .undeployed marker will stay there. Now when I
deploy again, it will finally be deployed. And I have these:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.deployed
{code}
Now I undeploy and I still have this:
{code}
jboss-as-kitchensink-html5-mobile.war.undeployed
{code}
And now the server stop fails. So I killed the process.
Another attempt now:
First I removed the remaining .undeployed marker.
Then I started the server.
Then I deployed something. Again, it copied over the content, but the console only said:
{code}
12:01:39,590 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
1) WFLYDS0004: Found jboss-as-kitchensink-html5-mobile.war in deployment directory. To
trigger deployment create a file called jboss-as-kitchensink-html5-mobile.war.dodeploy
{code}
The dir only contains the war now:
{code}jboss-as-kitchensink-html5-mobile.war{code}
This time, I use Full Publish on the module. Now it's deployed.
The dir has this:
{code}
jboss-as-kitchensink-html5-mobile.war
jboss-as-kitchensink-html5-mobile.war.deployed
{code}
Now I undeploy. There is still the .undeployed marker.
And now server stop works. Strange? Yes.
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)