--- Alessandro Ilardo <[EMAIL PROTECTED]> wrote: > back to my problem: I discovered that the kindly > network administrator > had configured two tomcat instances, one working > with apache connector > for the normal http request and the other on a > different port for the > ssl. Both instances get the classes from the same > directory, but > apparently on the one set for the ssl, reload > attribute was disabled for > some how. In another words it means that each time I > reloaded the tomcat > I only did it for the http connection.
Not sure why he had two instances for HTTPS vs HTTP. Apache filters out the encryption and passes off to Tomcat, so you should only have had to have Apache with the certificate installed, one tomcat instance (or multiple workers for session sharing), and there you go. Bad configuration. > > I have to say that I didn't have an easy life with > Apache http connector > and Tomcat, especially for what regards ssl. I > believe that for future > I'll opt for using tomcat as standalone webserver > which to serve html > pages too, instead to lose working days again. Yes if you are not going to use any Apache modules for anything it is a good option to just use Tomcat. I have a server running pure Tomcat, and I've had no problems, though once you have the connector and SSL setup for Apache there really isn't anything different from a plain install. What problems have you had really? Wade --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
