I am getting a whole lot of these warnings in my stderr.log each time a client connects via SSL. I have been using SSL since tomcat 3.x - and have never had any problems. Since I recently switched to 4.1.12 - I am assuming this is a coyote related Http11Processor bug?
I have noticed that it does even after following the SSL config howto. If the following is a meaningless error, it would be nice to shut it off so stderr.log doesn't grow so huge. WARNING: Exception getting SSL attributes javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(DashoA6275) at org.apache.tomcat.util.net.JSSESupport.getPeerCertificateChain(JSSESupport.java:118) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:543) at org.apache.coyote.Response.action(Response.java:216) at org.apache.coyote.tomcat4.CoyoteAdapter.postParseRequest(CoyoteAdapter.java:314) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:221) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533) at java.lang.Thread.run(Thread.java:536) Randy
