October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24868) Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 10/28/17 10:08 AM: --------------------------------------------------------------------- [~jeffmaury] so you think that also disabling the livenessProbe when debugging isnt required? Given that where livenessProbe(s) exist, the debugging session is still terminated I believe that we should disable those too. was (Author: adietish): [~jeffmaury] so you think that also disabling the livenessProbe when debugging isnt required? Given that where livenessProbe(s) exists, the debugging session is still terminated because of livenessProbe(s) I believe that we should disable those too. > Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > 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.2.AM1 > > Attachments: application-is-not-available.png, 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.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 10/28/17 10:07 AM: --------------------------------------------------------------------- [~jeffmaury] so you think that also disabling the livenessProbe when debugging isnt required? Given that where livenessProbe(s) exists, the debugging session is still terminated because of livenessProbe(s) I believe that we should disable those too. was (Author: adietish): [~jeffmaury] so you think that also disabling the livenessProbe when debugging isnt required? > Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > 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.2.AM1 > > Attachments: application-is-not-available.png, 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.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24868: ------------------------------------- Summary: Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property (was: Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: Switch off pod livenessProbe.periodSecond property and router timeout during debug session) > Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: set route timeout and disable pod livenessProbe.periodSecond property > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > 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.2.AM1 > > Attachments: application-is-not-available.png, 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.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: 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: ------------------------------------- Summary: Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (was: Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error)) > Server adapter: Node.js debug session terminated after 30s, browser shows 502 gateway error: 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.2.AM1 > > Attachments: application-is-not-available.png, 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.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24868: ------------------------------------- Summary: Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error) (was: Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session) > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session (Node.js debug session terminated after 30s, browser shows 502 gateway error) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 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.2.AM1 > > Attachments: application-is-not-available.png, 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.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-23422. -------------------------------------- Resolution: Duplicate Issue This is duplicate to JBIDE-24868 > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.5.1.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.5.1.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22773: ------------------------------------------ [~dbocharov] [~rob.stryker] [~jeffmaury] what's the state of this issue? The upstream issue was closed without fix. If this isnt even fixable we should close it as WONT_FIX > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: server > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22773 at 10/28/17 10:02 AM: --------------------------------------------------------------------- [~dbocharov] [~rob.stryker] [~jeffmaury] what's the state of this issue? The upstream issue was closed without fix. If this isnt even fixable we should close it as WONT_FIX, if not we should consider reopening the upstream issue. was (Author: adietish): [~dbocharov] [~rob.stryker] [~jeffmaury] what's the state of this issue? The upstream issue was closed without fix. If this isnt even fixable we should close it as WONT_FIX > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: server > Fix For: 4.5.x > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20569: ------------------------------------- Sprint: devex #140 November 2017 > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.5.2.AM1 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2017