Quoting "Bas A. Schulte" <[EMAIL PROTECTED]>:
If your site serves mostly semi-static content, your best bet is mod_proxy +
mod_cache + mod_disk_cache.
If you need to generate almost every page you serve because they pages are
customized for each visitor, go with mod_jk.
I am using the mod_proxy + mod_cache + mod_disk_cache approach in a high-load
site (10M pages served/day) because I have a Java CMS running on
Tomcat, and it
is working more than fine.
One note, if you are going to use mod_proxy + mod_cache + mod_disk_cache: my
setup was working perfect with Apache 2.0.54, but last week when I moved to
Apache 2.0.55 I started noticing some pages are not expired when its time
arrived. I have been unable to find an explanation for this odd behaviour, but
I am further investigating the problem. This is happening with GETs, so it's
unrelated to the POSTs bug, I think.
Hi,
we've got 2 tiers running, first one runs plain Apache, on the 2nd
tier we run Tomcat.
Now we need to run a webapp containing some servlets on the tomcat
box. The app is really a tier 1 application (some forms etc.).
Someone at work suggested we use mod_jk in the tier 1 Apache to get
incoming onto tomcat on tier 2. I figured: why not just setup a
reverse proxy with ProxyPass/ProxyPassReverse?
On httpd.conf on Apache put this in:
ProxyPass /somewere/ http://otherbox:8080/webapp/
ProxyPassReverse /somewere/ http://otherbox:8080/webapp/
What are the advantages/disadvantages of using mod_jk in a scenario
like this? I don't get a whole lot of clues when looking at the
connectors documentation page.
Thanks for any feedback,
Bas.
---------------------------------------------------------------------
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]
