We found the performance of Tomcat running SSL pretty useless in
production. Is fine for development, but in production we run Apache
HTTP in the front to off load the SSL number crunching into native code.
Works a treat. Also gives you the benifit of being able to load balance
multiple tomcats and to have apache serve up a maintenance page when we
update code. Seems Apache queues up requests better too.
Cheers,
Alex.
Jim Kennedy wrote:
-----Original Message-----
From: Jim Kennedy [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 12, 2004 3:37 PM
To: 'Tomcat Users List'
Subject: Using Tomcat's HTTP processor and SSL
I am considering using Tomcat alone as my HTTP server as well as my servlet
container with SSL. I know a lot of people use Apache HTTP Server instead
of Tomcat for this and Tomcat is just the servlet container only.
Is there any reason why I should not use just Tomcat alone for this. I'm
actually using JBOSS with Tomcat, but Tomcat still handles the HTTP
requests. I have no static pages on my site.
Seems like a hassle to configure a separate server (Apache HTTP) when I
don't have to.
Also, are there any difficulties configuring Tomcat with SSL? I am using v
4.1.28
Thanks for any help or suggestions.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
