Matt,
2 suggestions:
1. Upgrade your JDK to 1.4.x. JSSE is now integrated with the Java Runtime
and, you never know, this step alone might fix your problem.
2. Create and configure the SSL connector using the Admin tool instead of
manually editing server.xml.
Thanks. I tried both suggestions exhaustively but don't any much better
success.
I have apache running SSL on this same server. Should I be working on the
jk2 connector instead, to use Apache's SSL? That looked more complicated
at first.
Thanks,
Matt
Matt,
2 suggestions:
1. Upgrade your JDK
I'm using 4.1.27 on debian 3.0 with the JDK 1.3 from Blackdown, and the
last independent JSSE from Sun, the one intended for jdk1.3. Tomcat runs
as user tomcat4, whose home dir is /usr/share/tomcat4 and whose login
shell is /bin/false.
Tomcat runs fine when I don't try to get SSL working.
, instead of the default of 30 days, I did not
have the problem again.
-Original Message-
From: Matt Morgan [mailto:[EMAIL PROTECTED]
Sent: Thu 9/25/2003 3:24 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Configuring server.xml for SSL breaks
:
Subject: Configuring server.xml for SSL breaks Tomcat
I'm using 4.1.27 on debian 3.0 with the JDK 1.3 from Blackdown, and the
last independent JSSE from Sun, the one intended for jdk1.3. Tomcat runs
as user tomcat4, whose home dir is /usr/share/tomcat4 and whose login
: Configuring server.xml for SSL breaks Tomcat
Thanks. Well, the Tomcat docs don't say anything about what the default
expiry is for keys self-generated with keytool, but this is work that I
did all today, and in general I was trying to use the keys within
