[jbosstools-issues] [JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over

[Ondrej Dockal (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Dockal updated JBIDE-25923:
----------------------------------
    Steps to Reproduce: 
1. Install devstudio 11.3.0.GA (staging at the moment)
2. Start it, choose new empty workspace
3. Create new server adapter EAP 7.1
4. Download or add downloaded EAP 7.1 into wizard and create new server runtime
5. Finish creating adapter
6. Import new Maven project into workspace (Project Explorer -> Import -> Existing Maven project -> jbosstools-openshift)
7. Install required maven plugins that discovery offers
8. Restart devstudio
9. Start EAP server adapter
10. ASSERT: EAP is started and there is no re-deployment of standalone.vX.xml file in console view
Actual result: EAP is started (though, we have watched even problem starting adapter) and there is replaced standalone.vX.xml file over and over and redeployment take place also...

  was:
1. Install devstudio 11.3.0.GA (staging at the moment)
2. Start it, choose new empty workspace
3. Create new server adapter EAP 7.1
4. Download or add downloaded EAP 7.1 into wizard and create new server runtime
5. Finish creating adapter
6. Import new Maven project into workspace (Project Explorer -> Import -> Existing Maven project -> jbosstools-openshift)
7. Install required maven plugins that discovery offers
8. Restart devstudio
9. Start EAP server adapter
10. ASSERT: EAP is started and there is no re-deployment of standalone.vX.xml file in console view
Actual result: EAP is started (though, we have watched even problem starting adapter) and there is replaced standalone.vX.xml file over and over and redeployment take place also...

See:  !ServerAdapterEAP.gif! 



> 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
>         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}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)