[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14760: ------------------------------------------ The cause of this is a "misconfigured" server which does not have the correct servername or serveralias. in case of apache it is missing the following configuration which solves it: {code} <VirtualHost mydomain.com:443> ServerName mydomain.com ServerAlias www.mydomain.com {code} If the above is missing from apache the server is warning the client while TLS/SSL handshaking that the requested name is not recognized (Level: Warning, Description: Unrecognized Name), Server mydomain.com. JDK7 (not JDK6!) then reacts to it with a "Fatal, Description: Unexpected Message". This is an additional check in JDK7 which they refuse to correct: "7127374 : JSSE creates SSLProtocolException on (common) warning: unrecognized_name for SNI" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7127374 The only way to turn this off is to set a global system property to the jvm BEFORE any SSL library is loaded: {code} -Djsse.enableSNIExtension=false {code} The openshift-java-client currently sets this system property (https://github.com/adietish/openshift-java-client/blob/master/src/main/ja...) but it has no effect since it is not the first one to do SSL connections in Eclipse: {code: title=UrlConnectionHttpClient} // JDK7 bug workaround System.setProperty(SYSPROP_ENABLE_SNI_EXTENSION, "false"); {code} -- 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