Has the certificate the SSL/TLS connection uses expired? This will cause the TLS connection to fail to come up. Then, if you have a security constraint defined in your web.xml file that requires TLS for your initial pages, the redirect from your normal port to the TLS port will fail (since the TLS port is not active).
Thanks for the idea. Unfortunately, the keystore hasn't changed from the time when everything worked. It is a JKS keystore, contains two certificates. The one is the self-signed CA, the other is for the TLS connection, signed by that CA. Both valid until 2013, for another nine years. Tomcat 5.0.18 worked happily with that keystore for several months. Tomcat 5.0.25 also worked with it for several weeks, until I restarted it few days ago.
Besides, just the TLS connection not working is not the problem. When a TLS connector is present in conf/server.xml, nothing comes up, not even the normal port. The normal port (80) is open, but no requests are served. The TLS port isn't open at all, according to netstat.
Ciao, Igor
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
