Hello,
I am using Tomcat version 3.3.1 RC1. When running in secure mode (SSL), a
call to JavaScript’s window.open() function generates the error below.
The error occurs about 30% of the time, and is not related to the window
being launched (an html file with only tags causes the error as well as a
jsp with frames) nor to any other window.open() parameter.
The error appears hundreds of times in a log file when the product is in
use. Obviously, this will get to be a problem for our customers. My guess
is that the http connection is broken and Tomcat erroneously
reports this error as "WARNING" (or is it "FATAL"?) instead of reporting
this problem at a "DEBUG" or "AUDIT" level. I can’t completely turn off the
error logging for obvious reasons.
Has anyone else encountered this, or better yet, solved it?!
Thanks,
Rachel Parker
Network Intelligence Corporation
PoolTcpEndpoint: Handshake failed
java.net.SocketException: Socket closed
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a([DashoPro-V1.2-120198])
at
com.sun.net.ssl.internal.ssl.AppOutputStream.write([DashoPro-V1.2-120198])
at java.io.OutputStream.write(OutputStream.java:61)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake([DashoPro-V1.2-120
198])
at
org.apache.tomcat.util.net.JSSESocketFactory.handshake(JSSESocketFactory.jav
a:270)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:479)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:516)
at java.lang.Thread.run(Thread.java:484)
ThreadPool: Caught exception executing
org.apache.tomcat.util.net.TcpWorkerThread@5c97e4, terminating thread
java.lang.NullPointerException
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:498)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:516)
at java.lang.Thread.run(Thread.java:484)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
