]
Ondrej Dockal commented on JBIDE-25923:
---------------------------------------
[~mmalina] I tried playing around the issue and steps to reproduce and could not
reproduce. So it seems fine for me.
Started EAP 7.1 Server adapter is replacing deployment and
redeploying over and over
------------------------------------------------------------------------------------
Key: JBIDE-25923
URL:
https://issues.jboss.org/browse/JBIDE-25923
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.5.3.Final
Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
Reporter: Ondrej Dockal
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.6.0.AM1
Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif
When there is specific maven project imported in Project explorer (jbosstools-openshift),
Started EAP 7.1 server adapter is printing output where deployment scanner replaces
deployment and redeploy over and over again, see part of log:
{code}
15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010:
Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027:
Starting deployment of "standalone.xml" (runtime-name:
"standalone.xml")
15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027:
Starting deployment of "standalone.v2.xml" (runtime-name:
"standalone.v2.xml")
15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027:
Starting deployment of "standalone.last.xml" (runtime-name:
"standalone.last.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010:
Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010:
Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010:
Deployed "standalone.xml" (runtime-name : "standalone.xml")
15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028:
Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027:
Starting deployment of "standalone.v3.xml" (runtime-name:
"standalone.v3.xml")
15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027:
Starting deployment of "standalone.xml" (runtime-name:
"standalone.xml")
15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028:
Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027:
Starting deployment of "standalone.last.xml" (runtime-name:
"standalone.last.xml")
15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016:
Replaced deployment "standalone.last.xml" with deployment
"standalone.last.xml"
15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010:
Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
{code}