August 2017 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------- Sprint: devex #137 September 2017 > 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.AM2 > > 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, 7 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: breakpoint-suspend-thread.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.x > > 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, 7 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: ------------------------------------------ [~rhuss] as far as I can tell (didnt test extensively though, simply put a brk-point into some code I have in Eclipse) Eclipse is suspending the thread by default: !breakpoint-suspend-thread.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.x > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23436) Integration tests: Properties: assert that extended connection properties are displayed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23436?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23436: ------------------------------------- Labels: connection integration_tests properties (was: connection properties) > Integration tests: Properties: assert that extended connection properties are displayed > --------------------------------------------------------------------------------------- > > Key: JBIDE-23436 > URL: https://issues.jboss.org/browse/JBIDE-23436 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Labels: connection, integration_tests, properties > Fix For: 4.5.x > > Attachments: extended-connection-properties.png > > > In JBIDE-23148 we added the extended connection properties to the properties view. > !extended-connection-properties.png! > We should now have this covered in our integration tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23138) When a new project is created while creating a new app, it will not appear in the wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23138?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23138 at 8/30/17 9:43 AM: ------------------------------------------------------------------- [~jeffmaury] can you please add steps here? To me it's not fully clear which one of the 2 cases that I conceive is the one that this issue is covering: # Create an app where you dont have any project that exists: you get prompted # Create a project via the "New" button in the 1st wizard page of the application wizard Both cases work fine for me. Am I missing something? was (Author: adietish): [~jeffmaury] can you please add steps here? To me it's not fully clear which one of the 2 cases that I conceive is the one that this issue is covering: # Create an app where you dont have any project that exists: you get prompted # Create a project via the "New" button in the 1st wizard page of the application wizard Both cases worf fine for me. Am I missing something? > When a new project is created while creating a new app, it will not appear in the wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23138 > URL: https://issues.jboss.org/browse/JBIDE-23138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > When a new project is created while creating a new application, it appears in the Openshift explorer but it is not displayed in the project combox in the wizard -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23138) When a new project is created while creating a new app, it will not appear in the wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23138?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23138: ------------------------------------------ [~jeffmaury] can you still experience this issue? I did not face this for ages. > When a new project is created while creating a new app, it will not appear in the wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23138 > URL: https://issues.jboss.org/browse/JBIDE-23138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > When a new project is created while creating a new application, it appears in the Openshift explorer but it is not displayed in the project combox in the wizard -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22304: ------------------------------------- Issue Type: Enhancement (was: Bug) > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.5.x > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

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

by Roland Huß (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Roland Huß commented on JBIDE-24868: ------------------------------------ The OpenShift annotation for the route sounds promising and it would be the easiest way to solve this problem (if it works, never tried it). For the liveness probe, I think if the breakpoint suspends only the current thread there should be always another thread available to answer the liveness probe. Any modern IDE should give the option to choose to suspend the whole JVM (which might be necessary if you have to examine other threads e.g. for race time conditions) or only the thread on which the breakpoint is. A fix could be as simple as documenting this feature, recommending to use the suspend-on-thread-only. > 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.x > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20723) Application wizard: application is created even though I cancel the job

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20723?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20723: ------------------------------------- Summary: Application wizard: application is created even though I cancel the job (was: Application wizard: application is created even though I cancel je job) > Application wizard: application is created even though I cancel the job > ----------------------------------------------------------------------- > > Key: JBIDE-20723 > URL: https://issues.jboss.org/browse/JBIDE-20723 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.5.x > > > Once the Finish button in New OpenShift Application wizard is clicked a new application is created no matter what. Even if I click on a Cancel button next to the progress bar of creation process, it looks at first like the process stopped, but it still continues and in few moments a shell with created resources is shown. Can we do something about this? Otherwise cancel button just stop eclipse job and progress bar but it does not do anything more behind it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22386: ------------------------------------- Issue Type: Enhancement (was: Bug) > Server Editor: Select different service takes too long > ------------------------------------------------------ > > Key: JBIDE-22386 > URL: https://issues.jboss.org/browse/JBIDE-22386 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > Fix For: 4.5.x > > > Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening. > Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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