August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26159: ------------------------------------- Sprint: devex #153 August 2018 (was: devex #152 July 2018) > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.0.AM2 > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- 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.AM2 (was: 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.AM2 > > > 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-26159) Server adapter: debugging is not stopped if you delete the pod

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26159: ------------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.0.AM1) > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.0.AM2 > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26260) Create New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26260?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26260: ------------------------------- Sprint: devex #154 September 2018 > Create New and Noteworthy for 4.9.0.AM3 > --------------------------------------- > > Key: JBIDE-26260 > URL: https://issues.jboss.org/browse/JBIDE-26260 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26274) JSF New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26274?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26274: ---------------------------------- Assignee: Jeff MAURY > JSF New and Noteworthy for 4.9.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26274 > URL: https://issues.jboss.org/browse/JBIDE-26274 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for JSF 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26274) JSF New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26274?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26274: ------------------------------- Labels: task (was: ) > JSF New and Noteworthy for 4.9.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26274 > URL: https://issues.jboss.org/browse/JBIDE-26274 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for JSF 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26273) OpenShift New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26273?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26273: ---------------------------------- Assignee: Andre Dietisheim > OpenShift New and Noteworthy for 4.9.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26273 > URL: https://issues.jboss.org/browse/JBIDE-26273 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for OpenShift 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26273) OpenShift New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26273: ---------------------------------- Summary: OpenShift New and Noteworthy for 4.9.0.AM3 Key: JBIDE-26273 URL: https://issues.jboss.org/browse/JBIDE-26273 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk, openshift Reporter: Jeff MAURY Priority: Critical Fix For: 4.9.0.AM3 Andre Dietisheim, Search for your component's New and Noteworthy issues: Queries: * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for OpenShift by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for OpenShift 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26273) OpenShift New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26273?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26273: ------------------------------- Labels: task (was: ) > OpenShift New and Noteworthy for 4.9.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26273 > URL: https://issues.jboss.org/browse/JBIDE-26273 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for OpenShift 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26274) JSF New and Noteworthy for 4.9.0.AM3

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26274: ---------------------------------- Summary: JSF New and Noteworthy for 4.9.0.AM3 Key: JBIDE-26274 URL: https://issues.jboss.org/browse/JBIDE-26274 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html-source-editing, jsf Reporter: Jeff MAURY Priority: Critical Fix For: 4.9.0.AM3 Jeff MAURY, Search for your component's New and Noteworthy issues: Queries: * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for JSF by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-26260 #comment Create N&N for JSF 4.9.0.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- 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 August 2018