tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Smith" <>
Subject Re: Tomcat 3.2 SSL error:Error reading request
Date Sun, 15 Oct 2000 16:40:23 GMT
Hi Robert,

I can tell you keystores for 1.2 and 1.3 are not compatible
(at least in my experience). 

I ignored the note about compiling tomcat and was
able to get SSL working in tomcat standalone
configuration. See the Dasho-Pro reference? That's
a tag from deep in the Cipher suite. I'm almost
certain you need to backtrack and generate a fresh
keystore. import your RSA cert into that and make sure 
it is for "tomcat" with a password of "changeit". 

Verify that the keystore was generated with the same 
JDK that is used by tomcat. You mention using
different JDK's. I think this is where the problem is.

Good Luck,

  ----- Original Message ----- 
  From: Robert Oschwald 
  Sent: Friday, December 15, 2000 11:28 AM
  Subject: Tomcat 3.2 SSL error:Error reading request


  I'm currently stuck with my SSL enabling of tomcat 3.2 with a weird error message.
  As soon as I try to access SSL secured content, the following error occurs:

  2000-12-15 05:23:51 - ContextManager: Error reading request R( /) 400
  2000-12-15 05:23:51 - Ctx(  ): 400 R( /) null
  2000-12-15 05:23:51 - Ctx(  ): Handler null null
  2000-12-15 05:23:51 - Ctx(  ): IOException in: R( /) Socket closed
  2000-12-15 05:10:57 - Ctx(  ): IOException in: R( /) Socket closed

  After a while, the following exception is thrown:

          at javax.servlet.ServletInputStream.readLine(
          at org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(HttpR
          at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(
          at org.apache.tomcat.service.TcpWorkerThread.runIt(
          at org.apache.tomcat.util.ThreadPool$

  I've compiled tomcat 3.2 with SSL support (SSLSocketFactory was compiled successfully)
  as described in the Tomcal-SSL-Howto document.

  ALso, I've changed my jdk-1.3 (IBM) jre file as described.

  I had a problem adding my CERT to the keystore, where keytool always complained that the

  public keys are different between the stored and given key.
  I worked that around by deleting the keystore and let keytool create it during the CERT
  That worked.

  I will now try it again with the SUN JDK 1.3, maybe the IBM jdk doesn't work.

  Has anyone an idea what the problem is? Is this caused by a keystore problem reading my
  or is there any hint you can give me?

  Thanks in advance!


View raw message