October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio closed JBIDE-18445. -------------------------------- > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18445: --------------------------------- Fix Version/s: 4.2.0.CR2 > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18445) Create POC automated test for Arquillian - using Red Deer for UI automation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18445?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18445: -------------------------------------- The test is here: http://machydra.brq.redhat.com:8080/job/jbosstools.arquillian.bot.tests.poc/ > Create POC automated test for Arquillian - using Red Deer for UI automation > --------------------------------------------------------------------------- > > Key: JBIDE-18445 > URL: https://issues.jboss.org/browse/JBIDE-18445 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.CR1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18463: ------------------------------------- Estimated Difficulty: Medium > Connection Dialog: should be able to save connection even if it is not valid > ---------------------------------------------------------------------------- > > Key: JBIDE-18463 > URL: https://issues.jboss.org/browse/JBIDE-18463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > > Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. > We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18463: ---------------------------------------- Summary: Connection Dialog: should be able to save connection even if it is not valid Key: JBIDE-18463 URL: https://issues.jboss.org/browse/JBIDE-18463 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.2.0.CR1 Reporter: Andre Dietisheim Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18463) Connection Dialog: should be able to save connection even if it is not valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18463: ------------------------------------- Fix Version/s: 4.3.x > Connection Dialog: should be able to save connection even if it is not valid > ---------------------------------------------------------------------------- > > Key: JBIDE-18463 > URL: https://issues.jboss.org/browse/JBIDE-18463 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > > Currently one can only save a connection if it is valid (the user could connect using a valid server and credentials). If the settings are not valid, the connection is not saved since "Connect" (that saves the connection) wont ever get enabled. > We should allow the user to save a connection even if it is not valid (ex. SSL errors happens even though the conn is valid per se) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-18454 at 10/1/14 7:56 AM: ------------------------------------------------------------------- one can test this easily via openshift-java-client integration tests: * ASSERT: have java, maven, git installed * EXEC: {code}git clone git@github.com:openshift/openshift-java-client.git{code} * EXEC: {code}mvn clean verify -Dtest=APIResourceIntegrationTest -Dlibra_server=ec2-54-211-140-126.compute-1.amazonaws.com -Ddefault_rhlogin=demouser -Dhttps.proxyHost=file.rdu.redhat.com -Dhttps.proxyPort=3128 -Djsse.enableSNIExtension=false{code} was (Author: adietish): one can test this easily via openshift-java-client integration tests: * ASSERT: have java, maven, git installed * EXEC: {code}git clone git@github.com:openshift/openshift-java-client.git{code} * EXEC: {code}mvn clean verify -Dtest=APIResourceIntegrationTest -Dlibra_server=ec2-54-211-140-126.compute-1.amazonaws.com -Ddefault_rhlogin=ec2-user -Dhttps.proxyHost=file.rdu.redhat.com -Dhttps.proxyPort=3128 -Djsse.enableSNIExtension=false{code} > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-18454 at 10/1/14 7:56 AM: ---------------------------------------------------------------- Fedora19 and openjdk8 (build 1.8.0_20-ea-b17) works ok. Fedora19 and openjdk7 (1.7.0.65-2.5.1.2.fc19.x86_64) does not work. was (Author: mlabuda): openjdk8 works ok (build 1.8.0_20-ea-b17). > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18454: ------------------------------------------ one can test this easily via openshift-java-client integration tests: * ASSERT: have java, maven, git installed * EXEC: {code}git clone git@github.com:openshift/openshift-java-client.git{code} * EXEC: {code}mvn clean verify -Dtest=APIResourceIntegrationTest -Dlibra_server=ec2-54-211-140-126.compute-1.amazonaws.com -Ddefault_rhlogin=ec2-user -Dhttps.proxyHost=file.rdu.redhat.com -Dhttps.proxyPort=3128 -Djsse.enableSNIExtension=false{code} > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18454: --------------------------------------------- Tried on OSX: jdk1.7.0 build 1.7.0_45-b18 - works jdk1.8.0 build 1.8.0_20-b26 - works > Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18454 > URL: https://issues.jboss.org/browse/JBIDE-18454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: ssl-error-on-connect.png > > > In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client) > {code} > java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186) > at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877) > at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451) > at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413) > at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) > at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) > at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 October 2014