August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26331) Server adapter: switching maven profile (which determines the war name) won't undeploy the old war

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26331: ---------------------------------------- Summary: Server adapter: switching maven profile (which determines the war name) won't undeploy the old war Key: JBIDE-26331 URL: https://issues.jboss.org/browse/JBIDE-26331 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.9.0.AM2 Reporter: Andre Dietisheim steps: # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... # EXEC: import the "hello" maven project into your Eclipse # EXEC: create a server adapter and start it # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* # ASSERT: *"openshift"* maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed. # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile # ASSERT: Console output for oc rsync shows that a war "hello.war" was deployed Result: A new war "hello.war" was published but not deployed - no .dodeploy marker was created - , the old war "ROOT.war" was *NOT* removed and is still deployed. In the Pod log you see the following output for wildfly/eap {code} [0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To trigger deployment create a file called hello.war.dodeploy {code} {code} [0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war") {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26330: ---------------------------------------- Summary: Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project Key: JBIDE-26330 URL: https://issues.jboss.org/browse/JBIDE-26330 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.9.0.AM2 Reporter: Andre Dietisheim steps: # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... # EXEC: import the "hello" maven project into your Eclipse # EXEC: create a server adapter and start it # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... # ASSERT: *"openshift"* maven profile is selected # EXEC: Restart Eclipse # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... Result: Project "hello" still has *"openshift"* profile selected Expected result: Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26330) Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26330?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26330: ------------------------------------- Fix Version/s: 4.9.x > Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26330 > URL: https://issues.jboss.org/browse/JBIDE-26330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM2 > Reporter: Andre Dietisheim > Fix For: 4.9.x > > > steps: > # EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... > # EXEC: import the "hello" maven project into your Eclipse > # EXEC: create a server adapter and start it > # ASSERT: server adapter for project "hello" is *[Started, Synchronized]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > # ASSERT: *"openshift"* maven profile is selected > # EXEC: Restart Eclipse > # ASSERT: server adapter for project "hello" is *[Stopped, Republish]* > # EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... > Result: > Project "hello" still has *"openshift"* profile selected > Expected result: > Project "hello" still has *no profile* selected (starting the server adapter selects the "openshift" profile, while stopping it unselects it.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26180: ------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018, devex #154 September 2018 (was: devex #152 July 2018, devex #153 August 2018) > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA > Coming in the next update, some orbit changes: > * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > Also: > * reddeer 2.3 > * m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26299: ------------------------------- Sprint: devex #154 September 2018 > [Red Hat Central] Update to latest Sonarlint 3.6 > ------------------------------------------------ > > Key: JBIDE-26299 > URL: https://issues.jboss.org/browse/JBIDE-26299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM3 > > > Pull 3.6.0 from https://eclipse-uc.sonarlint.org/ > Check if we have fewer CVEs after update: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26312) Windows 7 slaves stall for 7 hours while recording test results?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26312?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26312: ---------------------------------- Assignee: Josef Kopriva (was: Pavol Srna) > Windows 7 slaves stall for 7 hours while recording test results? > ---------------------------------------------------------------- > > Key: JBIDE-26312 > URL: https://issues.jboss.org/browse/JBIDE-26312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM3 > Reporter: Nick Boldt > Assignee: Josef Kopriva > Fix For: 4.9.0.Final > > > This has been happening for a while now. > {code} > 20:24:20 Archiving artifacts > 20:50:34 Recording test results > (nothing happens for like 7 hours) > 04:09:55 Agent went offline during the build > 04:09:55 ERROR: Connection was broken: java.nio.channels.ClosedChannelException > 04:09:55 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) > 04:09:55 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) > 04:09:55 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) > 04:09:55 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 04:09:55 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 04:09:55 at java.lang.Thread.run(Thread.java:748) > {code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > Anyone have a clue why collecting junit results should take >7hrs on win7, but work fine on other OSes? > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26175) Cannot create server adapter for eap71-basic-s2i template from CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26175: ------------------------------------- Labels: application_wizard regression server_adapter upstream (was: regression upstream) > Cannot create server adapter for eap71-basic-s2i template from CDK > ------------------------------------------------------------------ > > Key: JBIDE-26175 > URL: https://issues.jboss.org/browse/JBIDE-26175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.6.0.Final > Environment: CDK: CDK v3.5.0-1 > Red Hat Developer Studio > Version: 12.0.0.GA > Build id: GA-v20180706-1014-B2970 > OS: Linux, v.4.17.3-200.fc28.x86_64, x86_64 / gtk 3.22.30, WebKit 2.20.3 > Java version: 1.8.0_172 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: application_wizard, regression, server_adapter, upstream > Fix For: 4.9.0.AM3 > > > I was not able to create server adapter for eap71-basic-s2i template application. > Pod error log: > {code:java} > --> Scaling eap-app-1 down to zero > --> Scaling eap-app-2 to 1 before performing acceptance check > error: update acceptor rejected eap-app-2: pods for rc 'myproject/eap-app-2' took longer than 600 seconds to become available > {code} > Error log from OpenShift console: > {code:java} > Readiness probe failed: { > "probe.eap.dmr.EapProbe": { > "probe.eap.dmr.ServerStatusTest": "running", > "probe.eap.dmr.DeploymentTest": "Exception executing test: unorderable types: Status() < Status()", > "probe.eap.dmr.BootErrorsTest": [ > { > "failed-operation": { > "operation": "deploy", > "address": [ > { > "deployment": "kitchensink.war" > } > ] > }, > "failure-description": "{\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"kitchensink.war\\\".FIRST_MODULE_USE\" => \"WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \\\"kitchensink.war\\\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\\\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\\\".statistics is already registered\"}}", > "failed-services": { > "jboss.deployment.unit.\"kitchensink.war\".FIRST_MODULE_USE": "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"kitchensink.war\"\n Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS\n Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered" > } > } > ] > } > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-664) Orca and flat review problems [EBZ#536974]

by Eric Williams (JIRA)

[ https://issues.jboss.org/browse/ERT-664?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-664: --------------------------------- Assignee: Eric Williams > Orca and flat review problems [EBZ#536974] > ------------------------------------------ > > Key: ERT-664 > URL: https://issues.jboss.org/browse/ERT-664 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Labels: SWT, bzira > > I can not read information present in the screen using flat review mode. > The problem can be reproduced in various parts such as in the > editor, in the package explorer, project explorer and etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26223) Server adapter: Error when starting server adapter: no rsync nor tar present in container

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26223?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26223: ------------------------------------- Summary: Server adapter: Error when starting server adapter: no rsync nor tar present in container (was: Server adapter: Error occurred during starting server adapter for nodejs app) > Server adapter: Error when starting server adapter: no rsync nor tar present in container > ----------------------------------------------------------------------------------------- > > Key: JBIDE-26223 > URL: https://issues.jboss.org/browse/JBIDE-26223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Andre Dietisheim > Labels: oc_binary, rsync, server_adapter > Fix For: 4.9.x > > Attachments: Screenshot_20180719_150025.png > > > I have encounter rsync error during starting up server adapter while trying out https://github.com/jbosstools/jbosstools-openshift/pull/1774 together with oc 3.11 built from source. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26223) Server adapter: Error occurred during starting server adapter for nodejs app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26223?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26223: ------------------------------------------ This is the exact same issue as I faced in JBIDE-25871. This usually happens for a freshly created container, rsync seems to be trying to sync too early, rsync daemon is not ready yet. Usually it won't happen if you then republish. [~odockal] Does this match your experience? > Server adapter: Error occurred during starting server adapter for nodejs app > ---------------------------------------------------------------------------- > > Key: JBIDE-26223 > URL: https://issues.jboss.org/browse/JBIDE-26223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Andre Dietisheim > Labels: oc_binary, rsync, server_adapter > Fix For: 4.9.x > > Attachments: Screenshot_20180719_150025.png > > > I have encounter rsync error during starting up server adapter while trying out https://github.com/jbosstools/jbosstools-openshift/pull/1774 together with oc 3.11 built from source. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018