November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16103: ------------------------------------- Attachment: (was: port-forwarding-stop-disabled.png) > Port Forwarding: "Start All" is enabled even though all ports are started > ------------------------------------------------------------------------- > > Key: JBIDE-16103 > URL: https://issues.jboss.org/browse/JBIDE-16103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16103: ------------------------------------- Attachment: port-forwarding-stop-disabled.png > Port Forwarding: "Start All" is enabled even though all ports are started > ------------------------------------------------------------------------- > > Key: JBIDE-16103 > URL: https://issues.jboss.org/browse/JBIDE-16103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16103: ------------------------------------- Attachment: port-forwarding-stop-disabled.png port-forwarding-start-enabled.png.png > Port Forwarding: "Start All" is enabled even though all ports are started > ------------------------------------------------------------------------- > > Key: JBIDE-16103 > URL: https://issues.jboss.org/browse/JBIDE-16103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16103: ------------------------------------- Attachment: (was: port-forwarding-stop-disabled.png) > Port Forwarding: "Start All" is enabled even though all ports are started > ------------------------------------------------------------------------- > > Key: JBIDE-16103 > URL: https://issues.jboss.org/browse/JBIDE-16103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16103?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16103: ------------------------------------- Attachment: port-forwarding-stop-disabled.png port-forwarding-start-enabled.png.png > Port Forwarding: "Start All" is enabled even though all ports are started > ------------------------------------------------------------------------- > > Key: JBIDE-16103 > URL: https://issues.jboss.org/browse/JBIDE-16103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16103) Port Forwarding: "Start All" is enabled even though all ports are started

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16103: ---------------------------------------- Summary: Port Forwarding: "Start All" is enabled even though all ports are started Key: JBIDE-16103 URL: https://issues.jboss.org/browse/JBIDE-16103 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Andre Dietisheim Fix For: 4.2.x Attachments: port-forwarding-start-enabled.png.png, port-forwarding-stop-disabled.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16102) Port forwarding: overly verbose error dialog when ssh session fails

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16102: ---------------------------------------- Summary: Port forwarding: overly verbose error dialog when ssh session fails Key: JBIDE-16102 URL: https://issues.jboss.org/browse/JBIDE-16102 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.1.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 4.2.0.Alpha1 Attachments: ssh-failed.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16102) Port forwarding: overly verbose error dialog when ssh session fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16102?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16102: ------------------------------------- Attachment: ssh-failed.png > Port forwarding: overly verbose error dialog when ssh session fails > ------------------------------------------------------------------- > > Key: JBIDE-16102 > URL: https://issues.jboss.org/browse/JBIDE-16102 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > Attachments: ssh-failed.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16100 at 11/25/13 5:55 AM: -------------------------------------------------------------------- [~mmurray] the N&N I just checked is wrong. I wrote {quote} To allow you to adjust timeouts when talking to your OpenShift server we now offer you a preferences page. {quote} and max corrected it to the current text: {quote} There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. The default is 240 seconds (4 minutes). You can try raise this value if you are getting time out errors when using OpenShift. {quote} As stated in JBIDE-15880 there are 4 different timeouts that may apply: {quote} 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {quote} The initial value (when user did not set anything) is 0 for the *openshift-java-client specific system property (2)*. Since there's no *jdk-wide HttpUrlConnection timeout (3)* by default, the *safe default of 2 Minutes (4)* would apply. There are thus 2 issues here: 1) The screenshot suggests that we have a default of 240 seconds (4 MInutes) which is wrong. We default to 0 2) There's nothing that tells the user that the safe default of 2 Minutes is applied. I suggest that we change the text in the preferences page and maybe update the N&N to reflect this? was (Author: adietish): [~mmurray] the N&N I just checked is wrong. I wrote {quote} To allow you to adjust timeouts when talking to your OpenShift server we now offer you a preferences page. {quote} and max corrected it to the current text: {quote} There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. The default is 240 seconds (4 minutes). You can try raise this value if you are getting time out errors when using OpenShift. {quote} As stated in JBIDE-15880 there are 4 different timeouts that may apply: {quote} 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {quote} The initial value (when user did not set anything) is 0 for the *openshift-java-client specific system property (2)*. Since there's no *jdk-wide HttpUrlConnection timeout (3)* by default, the *safe default of 2 Minutes* would apply. There are thus 2 issues here: 1) The screenshot suggests that we have a default of 240 seconds (4 MInutes) which is wrong. We default to 0 2) There's nothing that tells the user that the safe default of 2 Minutes is applied. I suggest that we change the text in the preferences page and maybe update the N&N to reflect this? > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Environment: Version: 7.1.0.CR1 > Build id: CR1-v20131124-0717-B560 > Build date: 20131124-0717 > Reporter: Michelle Murray > Assignee: Max Rydahl Andersen > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16100) OpenShift time out preference should show default 240 seconds and not 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16100 at 11/25/13 5:56 AM: -------------------------------------------------------------------- [~mmurray] the N&N I just checked is wrong. I wrote {quote} To allow you to adjust timeouts when talking to your OpenShift server we now offer you a preferences page. {quote} and max corrected it to the current text: {quote} There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. The default is 240 seconds (4 minutes). You can try raise this value if you are getting time out errors when using OpenShift. {quote} As stated in JBIDE-15880 there are 4 different timeouts that may apply: {quote} 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {quote} The initial value (when user did not set anything) is *0* for the *openshift-java-client specific system property (2)*. Since there's no *jdk-wide HttpUrlConnection timeout (3)* by default, the *safe default of 2 Minutes (4)* would apply. There are thus 2 issues here: 1) The screenshot suggests that we have a default of 240 seconds (4 MInutes) which is wrong. We default to 0 2) There's nothing that tells the user that the safe default of 2 Minutes is applied. I suggest that we change the text in the preferences page and maybe update the N&N to reflect this? was (Author: adietish): [~mmurray] the N&N I just checked is wrong. I wrote {quote} To allow you to adjust timeouts when talking to your OpenShift server we now offer you a preferences page. {quote} and max corrected it to the current text: {quote} There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. The default is 240 seconds (4 minutes). You can try raise this value if you are getting time out errors when using OpenShift. {quote} As stated in JBIDE-15880 there are 4 different timeouts that may apply: {quote} 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {quote} The initial value (when user did not set anything) is 0 for the *openshift-java-client specific system property (2)*. Since there's no *jdk-wide HttpUrlConnection timeout (3)* by default, the *safe default of 2 Minutes (4)* would apply. There are thus 2 issues here: 1) The screenshot suggests that we have a default of 240 seconds (4 MInutes) which is wrong. We default to 0 2) There's nothing that tells the user that the safe default of 2 Minutes is applied. I suggest that we change the text in the preferences page and maybe update the N&N to reflect this? > OpenShift time out preference should show default 240 seconds and not 0 > ----------------------------------------------------------------------- > > Key: JBIDE-16100 > URL: https://issues.jboss.org/browse/JBIDE-16100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Environment: Version: 7.1.0.CR1 > Build id: CR1-v20131124-0717-B560 > Build date: 20131124-0717 > Reporter: Michelle Murray > Assignee: Max Rydahl Andersen > Attachments: OpenShift_deftimeout.png > > > Click Window > Preferences > JBoss Tools > OpenShift. > Remote requests time out field states '0'. > !OpenShift_deftimeout.png! > If the default time out is 240 seconds (as stated in N&N) and I haven't changed the default time out, then this should read 240 - right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 November 2013