[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 9/30/14 3:10 PM:
-------------------------------------------------------------------
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{code}
I dont know yet why *#getSupportedCipherSuites* is never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory)
was (Author: adietish):
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{code}
I dont know yet why #getSupportedCipherSuites is never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory)
> 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)
10 years, 2 months
[JBoss JIRA] (JBDS-3141) Test victi.ms maven plugin works within jbds (or at least does not fail)
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3141?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3141:
------------------------------------
* Installed sample from: https://github.com/victims/victims-enforcer/tree/master/sample
* The following errors are seen in the Problems view - the 4th error is the error referred to by Burr:
The declared package "com.redhat.com.srt.sample" does not match the expected package "com.redhat.victimssample" App.java /sample/src/main/java/com/redhat/victimssample line 1 Java Problem
The declared package "com.redhat.com.srt.sample" does not match the expected package "com.redhat.victimssample" AppTest.java /sample/src/test/java/com/redhat/victimssample line 1 Java Problem
Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment. sample Build path JRE System Library Problem
maven-enforcer-plugin (goal "enforce") is ignored by m2e. pom.xml /sample line 56 Maven Project Build Lifecycle Mapping Problem
* After correcting the declared package errors, and after modifying the pom.xml file to reference version 1.3.5-SNAPSHOT of the enforcer plugin, it's possible to build/run the sample and get the expected error (clean compile jar:jar):
):
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for com.redhat.victimssample:sample:jar:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 33, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building sample 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ sample ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-victims-rule) @ sample ---
[INFO]
+=========================+
|VICTIMS-ENFORCER SETTINGS|
+=========================+
fingerprint = fatal
updates = auto
metadata = warning
[INFO] Last update was on Tue Sep 30 13:30:24 GMT-05:00 2014. Checking for new vulnerabilities at http://www.victi.ms/
[WARNING] Unable to update victims database! Your CVE records might be out of date.
[WARNING] The dependency junit-3.8.1 matches a vulnerability recorded in the victims database. [CVE-9999-999]
[WARNING] Rule 0: com.redhat.victims.VictimsRule failed with message:
+=======================+
|VULNERABILITY DETECTED!|
+=======================+
For more information visit:
- https://access.redhat.com/security/cve/CVE-9999-999
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.507 s
[INFO] Finished at: 2014-09-30T13:42:41-05:00
[INFO] Final Memory: 12M/295M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce-victims-rule) on project sample: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> Test victi.ms maven plugin works within jbds (or at least does not fail)
> ------------------------------------------------------------------------
>
> Key: JBDS-3141
> URL: https://issues.jboss.org/browse/JBDS-3141
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: maven
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Fix For: 8.0.0.CR2
>
>
> http://victi.ms has a maven plugin to check/assert maven dependencies have issues.
> should check how it works and if it works within eclipse
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[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 9/30/14 3:09 PM:
-------------------------------------------------------------------
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{code}
I dont know yet why #getSupportedCipherSuites is never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory)
was (Author: adietish):
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{code}
I dont know yet why both methods that return the list of ciphers are never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory)
> 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)
10 years, 2 months
[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 9/30/14 3:07 PM:
-------------------------------------------------------------------
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{code}
I dont know yet why both methods that return the list of ciphers are never called in my current testing (my initial idea was to have them returning all but the _DHE_ ciphers from the wrapped socket factory)
was (Author: adietish):
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{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)
10 years, 2 months
[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:
------------------------------------------
In a POC the following seems to work for me (not tested extensively yet):
{code}
SSLSocketFactory wrappingSocketFactory = new SSLSocketFactory() {
@Override
public Socket createSocket(InetAddress arg0, int arg1, InetAddress arg2, int arg3) throws IOException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(String arg0, int arg1, InetAddress arg2, int arg3) throws IOException,
UnknownHostException {
return socketFactory.createSocket(arg0, arg1, arg2, arg3);
}
@Override
public Socket createSocket(InetAddress arg0, int arg1) throws IOException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public Socket createSocket(String arg0, int arg1) throws IOException, UnknownHostException {
return socketFactory.createSocket(arg0, arg1);
}
@Override
public String[] getSupportedCipherSuites() {
return null;
}
@Override
public String[] getDefaultCipherSuites() {
return null;
}
@Override
public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
SSLSocket socket = (SSLSocket) socketFactory.createSocket(s, host, port, autoClose);
List<String> ciphers = new ArrayList<String>();
for (String cipher : socket.getEnabledCipherSuites()) {
if (!cipher.contains("_DHE_")) {
ciphers.add(cipher);
}
};
socket.setEnabledCipherSuites(ciphers.toArray(new String[ciphers.size()]));
return socket;
}
};
((HttpsURLConnection) connection).setSSLSocketFactory(wrappingSocketFactory);
{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)
10 years, 2 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick edited comment on JBIDE-16066 at 9/30/14 2:56 PM:
--------------------------------------------------------------------
[~rob.stryker] Is there a reason the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61?
I'm looking at it in master - https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or...
And EAP_61 is defined but not listed in the array. Just wondering why not? I'm using that in the WS tools to determine if a particular server is "supported" or not.
was (Author: bfitzpat):
[~rob.stryker] Is there a reason the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61?
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.CR2
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-16066:
-------------------------------------------
[~rob.stryker] Is there a reason the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61?
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.CR2
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months