Client authentication and customized error pages

[Gustavo Rodríguez]

   Hi everyone! We were working in this issue some time ago, and 
reported that when using the clientAuth="want" parameter, we got the 
following exception:

java.net.SocketException: Socket Closed   
   at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:177)

   We left it for some time, as mister Bill Barker had developed a 
patch that, according to changelog, was finally included in tomcat 
5.0.20. So, now we just downloaded tomcat 5.0.24 and tried this 
authentication mechanism again. This time we get a similar error, 
althought at a different place:

   2004-05-11 12:45:16 RequestDumperValve[localhost]: 
---------------------------------------------------------------
2004-05-11 12:45:18 [EMAIL PROTECTED]: 
Exception Processing ErrorPage[errorCode=400, location=/Error.do]
ClientAbortException:  javax.net.ssl.SSLException: Connection has been 
shutdown: javax.net.ssl.SSLException: java.net.SocketException: 
Connection reset
       at 
org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:331)
       at 
org.apache.coyote.tomcat5.OutputBuffer.flush(OutputBuffer.java:297)
       at 
org.apache.coyote.tomcat5.CoyoteResponse.flushBuffer(CoyoteResponse.java:537)
       at 
org.apache.coyote.tomcat5.CoyoteResponseFacade.flushBuffer(CoyoteResponseFacade.java:238)
       at 
org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:303)
       at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:147)
       at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
       at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
       at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
       at 
org.apache.catalina.valves.RequestDumperValve.invoke(RequestDumperValve.java:169)
       at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
       at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:535)
       at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
       at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
       at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
       at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
       at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
       at 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
       at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:793)
       at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:702)
       at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:571)
       at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644)
       at java.lang.Thread.run(Thread.java:534)

   Is the socket still being closed by tomcat somewhere? May there be 
anything we should change in our configuration?

   Thanks very much in advance.

   Regads,
         Gustavo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]