July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25679) New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25679?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25679: ------------------------------------- Fix Version/s: 4.9.x (was: 4.6.0.Final) > New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-25679 > URL: https://issues.jboss.org/browse/JBIDE-25679 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.9.x > > Attachments: OpenshiftOnlineNewProject.webm, image-2018-02-01-10-22-40-265.png > > > # ASSERT: make sure you dont have any project in OpenShift Online (https://console.starter-us-east-1.openshift.com or https://open.paas.redhat.com) > # EXEC: launch new application wizard > # ASSERT: you're prompted to provide the name for a new project that will be created > # EXEC: provide the name, hit "Finish" > Result: > !image-2018-02-01-10-22-40-265.png! > New Application wizard shows up with no project selected nor available in the project combo and thus no templates are listed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25592) Tests: fix OpenShiftSpringBootProfileDetectorTest

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25592?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25592: ------------------------------------- Sprint: devex #152 July 2018 > Tests: fix OpenShiftSpringBootProfileDetectorTest > ------------------------------------------------- > > Key: JBIDE-25592 > URL: https://issues.jboss.org/browse/JBIDE-25592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: test > Fix For: 4.9.0.AM1 > > > OpenShiftSpringBootProfileDetectorTest is currently being ignored because the test runs fine in Eclipse but fails in maven. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

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 updated JBIDE-25000: ------------------------------------- Fix Version/s: 4.9.0.AM1 (was: 4.9.x) > 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.0.AM1 > > 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, 8 months

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 updated JBIDE-25000: ------------------------------------- Sprint: devex #138 September 2017, devex #152 July 2018 (was: devex #138 September 2017, devex #151 June 2018) > 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.0.AM1 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25592) Tests: fix OpenShiftSpringBootProfileDetectorTest

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25592?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-25592: ---------------------------------------- Assignee: Dmitrii Bocharov > Tests: fix OpenShiftSpringBootProfileDetectorTest > ------------------------------------------------- > > Key: JBIDE-25592 > URL: https://issues.jboss.org/browse/JBIDE-25592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: test > Fix For: 4.9.0.AM1 > > > OpenShiftSpringBootProfileDetectorTest is currently being ignored because the test runs fine in Eclipse but fails in maven. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25592) Tests: fix OpenShiftSpringBootProfileDetectorTest

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25592?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25592: ------------------------------------- Fix Version/s: 4.9.0.AM1 > Tests: fix OpenShiftSpringBootProfileDetectorTest > ------------------------------------------------- > > Key: JBIDE-25592 > URL: https://issues.jboss.org/browse/JBIDE-25592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: test > Fix For: 4.9.0.AM1 > > > OpenShiftSpringBootProfileDetectorTest is currently being ignored because the test runs fine in Eclipse but fails in maven. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25592) Tests: fix OpenShiftSpringBootProfileDetectorTest

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25592?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25592: ------------------------------------- Fix Version/s: (was: 4.9.x) > Tests: fix OpenShiftSpringBootProfileDetectorTest > ------------------------------------------------- > > Key: JBIDE-25592 > URL: https://issues.jboss.org/browse/JBIDE-25592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: test > Fix For: 4.9.0.AM1 > > > OpenShiftSpringBootProfileDetectorTest is currently being ignored because the test runs fine in Eclipse but fails in maven. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25616: ------------------------------------------ upstream issue was resolved & closed. So we should now verify this. [~jkopriva] can you verify this please? > [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: docker_image, fis, upstream > Fix For: 4.9.0.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26160: ------------------------------------- Fix Version/s: 4.9.0.AM1 > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: server_adapter > Fix For: 4.9.0.AM1 > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-25616: ------------------------------------- Fix Version/s: 4.9.0.AM1 > [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: docker_image, fis, upstream > Fix For: 4.9.0.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018