You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Erik Gulliksen (maillist)" <ma...@perspektiver.net> on 2006/04/04 20:59:50 UTC
Connecting Apache 2.2 and Tomcat 5.5.16
Hi there =)
I've been trying to figure out how to get my Tomcat 5.5.16 to play with an
Apache 2.2. (and Linux)
I'm new to configuring these applications and seem to get lost in the
documentation.
mod_jk, mod_jk2 (same as jk2?), mod_proxy, mod_proxy_balancer, mod_proxy_ajp
APR, AJP etc. and my head starts spinning.. :o\
Well basically what I though was to set up an Apache server and more then
one Tomcat servers with some load balancing. Am I wrong if I have the
impression that Apache is the way to go with 128bit SSL and as the front end
for load balancing?
Everything else should be handled by Tomcat, even static content I think.
(Thinking of some hardware SSL offloader if Apache don't handle it all that
well. Too bad they are not free too ;)
First of all giving my wishes, what connection type should I use?
Then how to write the proper configuration settings for my Tomcat and Apache
versions?
And last, how much load can an Apache server and Tomcat server expect to
handle of request/sec?
Happy for any response, or links to some easy to step by step guides.
Thanks in advance!
Regards,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: SV: Connecting Apache 2.2 and Tomcat 5.5.16
Posted by Bernie Durfee <be...@suny.edu>.
I believe that's it, although someone who knows more about the load balancing might know better. I built Apache 2.2.0
with the following configure arguments...
--enable-ssl=shared --enable-proxy=shared --enable-proxy-ajp=shared
...which created the .so shared modules: mod_ssl, mod_proxy, and mod_proxy_ajp.
Bernie
Erik Gulliksen (maillist) wrote:
> For my contect I have a feeling I would need these modules;
> - mod_proxy
> - mod_proxy_ajp
> - mod_proxy_balancer
> - mod_ssl
>
> Anything else I need to set up? (And if so, why?)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
SV: Connecting Apache 2.2 and Tomcat 5.5.16
Posted by "Erik Gulliksen (maillist)" <ma...@perspektiver.net>.
Thanks! This sounds promising :D
I guess I need to figure out what modules I need to load etc.
It seems like my Apache installation don't have any
mod_proxy_ajp.so (or what the name is).
I think I'll need to fiddle with my server and see what else is running.
For my contect I have a feeling I would need these modules;
- mod_proxy
- mod_proxy_ajp
- mod_proxy_balancer
- mod_ssl
Anything else I need to set up? (And if so, why?)
My plan was to remove as much modules etc. as possible.
-Erik
-----Opprinnelig melding-----
Fra: Bernie Durfee [mailto:bernard.durfee@suny.edu]
Sendt: 4. april 2006 21:10
Til: Tomcat Users List
Emne: Re: Connecting Apache 2.2 and Tomcat 5.5.16
> mod_jk, mod_jk2 (same as jk2?), mod_proxy, mod_proxy_balancer,
mod_proxy_ajp
> APR, AJP etc. and my head starts spinning.. :o\
From what I understand, as of Apache 2.2, the mod_jk project no longer
applies. Instead, the mod_proxy module is a
generic way to proxy from Apache HTTPD to other servers. So for Tomcat, the
mod_proxy_ajp module will proxy from Apache
HTTPD directly to Tomcat using the AJP protocol. This is much simpler than
ever, here is how I do it for one of my
servers...
<VirtualHost 12.34.56.78:80>
ServerName my.server.com
ProxyPreserveHost On
ProxyPass / ajp://12.34.56.78:8009/
</VirtualHost>
...which passes all requests for my.server.com to Tomcat, with an AJP
connector listening on port 8009...
<Connector address="12.34.56.78"
port="8009"
protocol="AJP/1.3"
enableLookups="false"
minSpareThreads="20"
maxSpareThreads="100"
maxThreads="200"
connectionTimeout="60000"
/>
...it's very simple now, no workers.properties or crazy mod_jk directives.
In fact mod_proxy_ajp is included with Apache
2.2.
> Well basically what I though was to set up an Apache server and more then
> one Tomcat servers with some load balancing. Am I wrong if I have the
> impression that Apache is the way to go with 128bit SSL and as the front
end
> for load balancing?
I have it set for SSL, which still uses the exact same proxy diretives,
since the proxying is done using AJP after
Apache does all the SSL protocol stuff. Again, very simple. As for load
balancing, I believe this would be handed by
some additional mod_proxy directives.
Bernie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Connecting Apache 2.2 and Tomcat 5.5.16
Posted by Bernie Durfee <be...@suny.edu>.
> mod_jk, mod_jk2 (same as jk2?), mod_proxy, mod_proxy_balancer, mod_proxy_ajp
> APR, AJP etc. and my head starts spinning.. :o\
From what I understand, as of Apache 2.2, the mod_jk project no longer applies. Instead, the mod_proxy module is a
generic way to proxy from Apache HTTPD to other servers. So for Tomcat, the mod_proxy_ajp module will proxy from Apache
HTTPD directly to Tomcat using the AJP protocol. This is much simpler than ever, here is how I do it for one of my
servers...
<VirtualHost 12.34.56.78:80>
ServerName my.server.com
ProxyPreserveHost On
ProxyPass / ajp://12.34.56.78:8009/
</VirtualHost>
...which passes all requests for my.server.com to Tomcat, with an AJP connector listening on port 8009...
<Connector address="12.34.56.78"
port="8009"
protocol="AJP/1.3"
enableLookups="false"
minSpareThreads="20"
maxSpareThreads="100"
maxThreads="200"
connectionTimeout="60000"
/>
...it's very simple now, no workers.properties or crazy mod_jk directives. In fact mod_proxy_ajp is included with Apache
2.2.
> Well basically what I though was to set up an Apache server and more then
> one Tomcat servers with some load balancing. Am I wrong if I have the
> impression that Apache is the way to go with 128bit SSL and as the front end
> for load balancing?
I have it set for SSL, which still uses the exact same proxy diretives, since the proxying is done using AJP after
Apache does all the SSL protocol stuff. Again, very simple. As for load balancing, I believe this would be handed by
some additional mod_proxy directives.
Bernie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org