September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4571) SWTException prevents Getting Started tab from populating

by Roland Grunberg (JIRA)

Roland Grunberg created JBDS-4571: ------------------------------------- Summary: SWTException prevents Getting Started tab from populating Key: JBDS-4571 URL: https://issues.jboss.org/browse/JBDS-4571 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Affects Versions: 11.0.0.GA Environment: Fedora 26 x86_64 webkitgtk4-2.16.6-1.fc26.x86_64 devstudio-11.0.0.GA-installer-standalone.jar openjdk version "1.8.0_144" OpenJDK Runtime Environment (build 1.8.0_144-b01) OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode) Reporter: Roland Grunberg # Using the Devstudio installer ($ java -jar /notnfs/Downloads/devstudio-11.0.0.GA-installer-standalone.jar), I installed in '/notnfs/devstudio' (not in a home folder), with the default system JVM. # On startup (can be from the install, or separately), create a workspace in $HOME/workspace-devstudio. # Red Hat Central view loads, with the 'Do Not Enter' icon and the text 'An exception was raised in Javascript'. Clicking on the 'Details >>' button shows the full stacktrace, and it is not logged into the Error Log view. Note that switching to the Software/Update tab gets the Red Hat Central view to become populated with the correct content so the issue seems isolated to the 'Getting Started' tab. https://paste.fedoraproject.org/paste/Y5jrMNBt86LoEAsqIGykTg The relevant part seems to be : org.eclipse.swt.SWTException: An exception was raised in JavaScript at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273) at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324) at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409) at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663) at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610) at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51) at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188) at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/28/17 9:43 AM: ------------------------------------------------------------------- According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently *v1.RouteTargetReference* || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers. Matching this is the fact that the web-ui hard coded the service in the form to edit/create a route: !webui_edit-add-service.png! was (Author: adietish): According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently *v1.RouteTargetReference* || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers. Matching this is the fact that the web-ui hard coded the service in the form to edit/create a route: > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24868: ------------------------------------- Attachment: webui_edit-add-service.png > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png, webui_edit-add-service.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/28/17 9:42 AM: ------------------------------------------------------------------- According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently *v1.RouteTargetReference* || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers. Matching this is the fact that the web-ui hard coded the service in the form to edit/create a route: was (Author: adietish): According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently *v1.RouteTargetReference* || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/28/17 9:35 AM: ------------------------------------------------------------------- According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently *v1.RouteTargetReference* || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers was (Author: adietish): According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently **v1.RouteTargetReference** || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/28/17 9:35 AM: ------------------------------------------------------------------- According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently **v1.RouteTargetReference** || name || value || | kind | The kind of target that the route is referring to. Currently, *only 'Service' is allowed*| We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers was (Author: adietish): According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently v1.RouteTargetReference || name || value || | kind | The kind of target that the route is referring to. Currently, only 'Service' is allowed We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/28/17 9:35 AM: ------------------------------------------------------------------- According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently v1.RouteTargetReference || name || value || | kind | The kind of target that the route is referring to. Currently, only 'Service' is allowed We can thus only change the timeouts for applications that have services. We wont be able to find the route for application where there are only deployment configs or replication controllers was (Author: adietish): According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently ``` v1.RouteTargetReference || name || value || | kind | The kind of target that the route is referring to. Currently, only 'Service' is allowed ``` > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ According to https://docs.openshift.com/container-platform/3.6/rest_api/openshift_v1.h... only routes whih point to a service are supported currently ``` v1.RouteTargetReference || name || value || | kind | The kind of target that the route is referring to. Currently, only 'Service' is allowed ``` > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM3 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 commented on JBIDE-25000: ------------------------------------------ I can't reproduce this in my current CDK which seems faster after a fresh install. Since this can be worked around by restarting the adapter, I deem this not critical and postpone it. > 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 > Fix For: 4.5.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in OpenShift 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.2.3#72005)

8 years, 6 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.5.x (was: 4.5.1.AM3) > 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 > Fix For: 4.5.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in OpenShift 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.2.3#72005)

8 years, 6 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 September 2017