August 2018 - jbosstools-issues - Jboss List Archives

[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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25000: ------------------------------------------ Still no obvious solution in our code, nothing worked. Have to discuss it with openshift-dev, suggesting that a readyness-probe for the debugging port should be added in case debugging is enabled. > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

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 updated JBIDE-26223: ------------------------------------- Steps to Reproduce: 1. Create and Start CDK 3.2+ server adapter using newest CDK (v3.5.0) 2. Preferences -> Openshift 3 -> add path to oc 3. Add new application into running OS3 connection (nodejs) 4. Create new server adapter for this app 5. Adapter is created and started succesfully Actual result: Adapter is started, but I got this error: !Screenshot_20180719_150025.png|thumbnail! was: 1. Create and Start CDK 3.2+ server adapter using newest CDK (v3.5.0) 2. Preferences -> Openshift 3 -> add path to oc 3.11 3. Add new application into running OS3 connection (nodejs) 4. Create new server adapter for this app 5. Adapter is created and started succesfully Actual result: Adapter is started, but I got this error: !Screenshot_20180719_150025.png|thumbnail! > 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018