Apr 26, 2005 2:19:46 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
SEVERE: Endpoint [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=443]] ignored exception: java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate corresponds to the SSL cipher suites which are enabled.
java.net.SocketException: SSL handshake errorjavax.net.ssl.SSLException: No available certificate corresponds to the SSL cipher suites which are enabled.
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket(JSSESocketFactory.java:152)
at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:371)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:553)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
at java.lang.Thread.run(Thread.java:534)
Apr 26, 2005 2:19:46 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket
WARNING: Reinitializing ServerSocket
Thoughts?
Jeff
Jason Bainbridge wrote:
On 4/26/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Actually, I did not start with the old cert. I generated a completely new cert, started with the chaincert, then imported the new cert that verisign sent back.
This is the connector tect:
<Factory
className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"clientAuth="false"
protocol="TLS" keystorefile="/usr/local/qmetrix/.keystore" keystorePass=
Is that a copy and paste? If so you're going to first want to make sure there are no sharp instruments around and then change keystorefile to keystoreFile as it's case sensitive, then restart Tomcat. With it lower case like that it will still look in the default location and would expain the behaviour you are seeing.
However if that isn't the case then we have some more digging to do.
Regards,
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
