Hi,
I have a java applet that I use for signing files before they are posted
to my tomcat server. The applet is accessed through a simple JSP page.
Since the applet must have access to the client file system, it is
signed by my keystore. I can successfully sign files over http, however,
some problems occur when I migrated over to https, particulary when
using client authentication.
Strange things occur when the applet is accessed over https with client
authentication. The catalina.out logs write this message whenever the
page is accessed:
04-Aug-2004 19:05:05 org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Remote Host /152.78.69.24 SocketException: Broken pipe
04-Aug-2004 19:05:05 org.apache.tomcat.util.net.TcpWorkerThread runIt
SEVERE: Remote Host /152.78.69.24 SocketException: Broken pipe
The java console on the client reports similar problems, but in a
verbose manner:
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:282)
at
com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:271)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:663)
....
.... the same exception repeats 17 times!
load: class SignFilesApplet not found.
java.lang.ClassNotFoundException: SignFilesApplet
at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:164)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
....
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:282)
at
com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:271)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:663)
....
I've heavily abbreviated these exceptions to ease the reading. I can
provide a full stack trace if required.
I have no problems downloading the applet when only the server is
authenticated over https.
I am running jakarta-tomcat-5.0.25, with j2sdk1.4.2_04. The applet has
been tested using j2sdk1.4.2_04 and j2sdk1.5.0 with identical results.
Firefox 0.9.1 is used for the browser.
If anyone can provide some insight as to why the is causing the socket
exception, I would be most appreciative.
Best Regards,
Rowland Watkins
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
