[jbosstools-issues] [JBoss JIRA] (JBIDE-14024) war deployed to remote as7/eap6 is undeployed immediately
[
https://issues.jboss.org/browse/JBIDE-14024?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-14024.
---------------------------------
Labels: (was: respin-b)
Resolution: Done
It seems this issue was fixed last week during other related enhancements to management
scanning. See commit [1]
The problem here came up when we changed the workflow order. Previously, the deployment
scanner modifiers were listeners who responded to the server state. One api was used to
initiate the scanner changes, and this api checked whether the scanner could
'accept' the changed server.
This was changed to the server behavior itself 'kicking off' the scanner
modifiers, and they used a newer api which did not check whether the scanner
'accepted' the server. This was bc it was assumed the server itself was kicking
off the event, so it DID apply.
This was a faulty assumption, and was fixed during routine cleanup and enhancements. See
the commit for more information.
[1]
https://github.com/jbosstools/jbosstools-server/commit/2c864c59ce5795bd54...
war deployed to remote as7/eap6 is undeployed immediately
---------------------------------------------------------
Key: JBIDE-14024
URL: https://issues.jboss.org/browse/JBIDE-14024
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.0.Alpha2
Environment: JBDS 7.0.0.Alpha2 B135
EAP 6.1.0.ER4 / EAP 6.0.1 / AS 7.1.1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.1.0.Beta1
When I set up a remote EAP 6.1 with the management port enabled and then try to deploy a
dynamic web project (exploded war), it gets deployed, but then undeployed right
afterwards.
This is in the remote server log:
{code}
12:00:39,808 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a
file called dynproj.war.dodeploy
12:00:43,746 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a
file called dynproj.war.dodeploy
12:00:43,750 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "dynproj.war" (runtime-name: "dynproj.war")
12:00:43,811 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register
web context: /dynproj
12:00:43,923 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559:
Deployed "dynproj.war" (runtime-name : "dynproj.war")
12:00:48,932 INFO [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224:
Unregister web context: /dynproj
12:00:48,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877:
Stopped deployment dynproj.war (runtime-name: dynproj.war) in 22ms
12:00:49,041 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558:
Undeployed "dynproj.war" (runtime-name: "dynproj.war")
12:00:54,043 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a
file called dynproj.war.dodeploy
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira