"I'm not sure how (or even if) you can have Java attempt to connect
with SSLv3 and then re-try with TLS."
I think it is possible, have a look on JSSE Reference Guide for
sun.security.ssl.allowUnsafeRenegotiation and
sun.security.ssl.allowLegacyHelloMessages, they're explaining how to
catch the SSL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Deepak,
On 2/25/15 1:49 AM, dku...@ccilindia.co.in wrote:
>> Perhaps you disabled SSLv3 and a client is trying to connect
>> using SSLv3?
>
> We agree with your above statement. We have disabled SSLv3 on
> Tomcat server and our client is an exe whi
From: Christopher Schultz
To: Tomcat Users List
Date: 24-02-2015 20:36
Subject:Re: Getting javax.net.ssl.SSLHandshakeException
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Deepak,
On 2/24/15 9:19 AM, dku...@ccilindia.co.in wrote:
> We have migrated from apache tomcat 8.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Deepak,
On 2/24/15 9:19 AM, dku...@ccilindia.co.in wrote:
> We have migrated from apache tomcat 8.0.8 to apache tomcat
> 8.0.18.(to prevent the poodle attack).
Note that upgrading Tomcat is not necessary to mitigate SSL POODLE.
Upgrading does have
Dear All,
We have migrated from apache tomcat 8.0.8 to apache tomcat 8.0.18.(to
prevent the poodle attack). But now we are facing the below issue.
javax.net.ssl.SSLHandshakeException: Remote host closed connection during
handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecor
