Re: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.

___ From: Estanislao Gonzalez To: Tomcat Users List Sent: Wed, August 11, 2010 7:59:07 AM Subject: Re: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled. Hi, Just in case this is als

Re: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.

: Tomcat Users List Sent: Wed, August 11, 2010 7:59:07 AM Subject: Re: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled. Hi, Just in case this is also related to my problem that

Re: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.

Hi, Just in case this is also related to my problem that truststoreFile is not being read while redirecting from http. Check pointing to the file with the JVM param: -Djavax.net.ssl.trustStore= And if this works but your truststoreFile param at the connector don't write some feedback. thank

RE: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.

We got that early on when we first started working SSL secured sockets in our app and it was due to us not actually pointing to the correct certificate files and instead still going for the older ones. Is this a possibility in your situation?