[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25923 at 4/17/18 10:25 AM:
-----------------------------------------------------------------
I am going to record some gif file to show that this is really happening: ServerAdapterEAP.gif
was (Author: odockal):
I am going to record some gif file to show that this is really happening.
> 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25923:
----------------------------------
Workaround Description:
1. Close imported projects that brought Error into Problems view. (Maybe just a coincidence).
2. Restart server adapter
was:
1. Close imported projects that brought Error into Problems view. (Maybe just a coincidence).
2. Restart server adapter
See: !ServerAdapterEAPRepaired.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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25923:
---------------------------------------
To see how to repair eap deployment-scanner component, watch: ServerAdapterEAPRepaired.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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25923:
----------------------------------
Attachment: ServerAdapterEAPRepaired.gif
ServerAdapterEAP.gif
Workaround Description:
1. Close imported projects that brought Error into Problems view. (Maybe just a coincidence).
2. Restart server adapter
> 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25923:
----------------------------------
Workaround Description:
1. Close imported projects that brought Error into Problems view. (Maybe just a coincidence).
2. Restart server adapter
See: !ServerAdapterEAPRepaired.gif!
was:
1. Close imported projects that brought Error into Problems view. (Maybe just a coincidence).
2. Restart server adapter
> 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
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...
See: !ServerAdapterEAP.gif!
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...
> 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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
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)
7 years, 11 months
[JBoss JIRA] (JBIDE-25644) Delete Resources: Scrollbars are not visible, scrolling stops working after resize
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25644?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25644:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.5.3.Final)
> Delete Resources: Scrollbars are not visible, scrolling stops working after resize
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25644
> URL: https://issues.jboss.org/browse/JBIDE-25644
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + DevStudio 11.2.0.GA, Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: delete_resources
> Fix For: 4.5.x
>
> Attachments: image-2018-01-24-15-34-06-459.png, image-2018-01-24-15-34-31-837.png, image-2018-01-24-15-35-04-125.png
>
>
> I have found several UI errors in this dialog:
> - Scrolling bars not visible on Fedora (I have not tested it on other OS yet)
> - After resize scrolling stops working
> - When I enter simple label (e.g. camel), results after deleting label are different:
> Before entering:
> !image-2018-01-24-15-34-06-459.png|thumbnail!
> With label:
> !image-2018-01-24-15-34-31-837.png|thumbnail!
> After deleting label:
> !image-2018-01-24-15-35-04-125.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25700:
-------------------------------------
Fix Version/s: 4.6.0.AM1
(was: 4.5.x)
> Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25700
> URL: https://issues.jboss.org/browse/JBIDE-25700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: server_adapter, springboot
> Fix For: 4.6.0.AM1
>
> Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png
>
>
> neither with open.paas.redhat.com
> so only when using the CDK.
> it seems to be due to the fact that the user in the pod are not the same.
> Jeff said:
> {quote}
> For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF
> The user permissions on those folders are the following:
> /deployments: writable by user jboss and group root
> /deployments/BOOT-INF: writable by user jboss readable only by group root
> /deployments/META-INF: writable by user jboss readable only by group root
> The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months