« Return to Thread: Apache configuration.
Re: Apache configuration.
by R.P. Aditya
::
Rate this Message:
Reply (Restricted by the Administrator) | View in Thread
On Fri, Dec 14, 2007 at 05:45:51PM -0800, Eric Hattemer wrote:
> If you don't really need apache to be the frontend, the simple fix is to
> go into tomcat's server.xml, replace 8080 with 80, and replace 8443 with
> 443.
but then you have to run tomcat as root or allow non-root users to bind to
privileged ports (or run Windows which is saying the same thing)
> What are the most popular production environments? mod_jk? Proxying?
> Simple Tomcat? Tomcat Clustering? Is there an advantage to anything
> above Simple tomcat if all the pages are served by tomcat anyway?
UM uses Apache+mod_jk -- there are a few advantages:
- serving static content with Apache avoids using a thread per request in
Tomcat, which is key for Tomcat scalability (if you have presence turned off,
about 40+% of hits are for static content typically, depending on your
expiration policy)
- Apache native SSL is much faster than Tomcat SSL unless you use APR
- In our case, our SSO Apache module (Cosign -- www.weblogin.org) is better
tested and capable than the Java filter version
- there is no equivalent to mod_security in Tomcat :-)
more reasons via Google including at:
http://wiki.apache.org/tomcat/FAQ/Connectors
Hope that helps,
Adi
> Galina Manirko wrote:
> >Hello Sakai Development Group!
> >
> >
> >
> >I need to configure Apache HTTP server to be in front of my Tomcat
> >server that runs Sakai. Could you, please, tell me if we have somewhere
> >a detailed instruction on how to implement this task? I try to follow
> >the instruction in 'Sakai 2.4 Admin Guide - Advanced Tomcat (and Apache)
> >Configuration' but my knowledge in Apache configuration is so poor that
> >I cannot make it work; I keep getting error message 'Service is not
> >available'.
> >
> >I would really appreciate if you can help me with this problem.
> >
> >
> >
> >Regards
> >
> >Galina Manirko
> >
> >Network Administrator
> >
> >Alameda County Office of Education
> >
> >
> >
> >P.S. We use Sakai v.2.4 on Tomcat-5.5.23 and Apache 2.2 on Red Hat
> >Linux.
> >
> >[see attachment: "message0.html", size: 4572 bytes]
> >
> >
> >Attachments:
> >
> >message0.html
> >https://collab.sakaiproject.org/access/content/attachment/c729edb8-79e4-45a2-0061-91c251d9300f/message0.html
> >
> >----------------------
> >This automatic notification message was sent by Sakai Collab
> >(https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a.
> >sakai-dev) site.
> >You can modify how you receive notifications at My Workspace > Preferences.
> >
> >
>
> ----------------------
> This automatic notification message was sent by Sakai Collab
> (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a.
> sakai-dev) site.
> You can modify how you receive notifications at My Workspace > Preferences.
>
----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.
> If you don't really need apache to be the frontend, the simple fix is to
> go into tomcat's server.xml, replace 8080 with 80, and replace 8443 with
> 443.
but then you have to run tomcat as root or allow non-root users to bind to
privileged ports (or run Windows which is saying the same thing)
> What are the most popular production environments? mod_jk? Proxying?
> Simple Tomcat? Tomcat Clustering? Is there an advantage to anything
> above Simple tomcat if all the pages are served by tomcat anyway?
UM uses Apache+mod_jk -- there are a few advantages:
- serving static content with Apache avoids using a thread per request in
Tomcat, which is key for Tomcat scalability (if you have presence turned off,
about 40+% of hits are for static content typically, depending on your
expiration policy)
- Apache native SSL is much faster than Tomcat SSL unless you use APR
- In our case, our SSO Apache module (Cosign -- www.weblogin.org) is better
tested and capable than the Java filter version
- there is no equivalent to mod_security in Tomcat :-)
more reasons via Google including at:
http://wiki.apache.org/tomcat/FAQ/Connectors
Hope that helps,
Adi
> Galina Manirko wrote:
> >Hello Sakai Development Group!
> >
> >
> >
> >I need to configure Apache HTTP server to be in front of my Tomcat
> >server that runs Sakai. Could you, please, tell me if we have somewhere
> >a detailed instruction on how to implement this task? I try to follow
> >the instruction in 'Sakai 2.4 Admin Guide - Advanced Tomcat (and Apache)
> >Configuration' but my knowledge in Apache configuration is so poor that
> >I cannot make it work; I keep getting error message 'Service is not
> >available'.
> >
> >I would really appreciate if you can help me with this problem.
> >
> >
> >
> >Regards
> >
> >Galina Manirko
> >
> >Network Administrator
> >
> >Alameda County Office of Education
> >
> >
> >
> >P.S. We use Sakai v.2.4 on Tomcat-5.5.23 and Apache 2.2 on Red Hat
> >Linux.
> >
> >[see attachment: "message0.html", size: 4572 bytes]
> >
> >
> >Attachments:
> >
> >message0.html
> >https://collab.sakaiproject.org/access/content/attachment/c729edb8-79e4-45a2-0061-91c251d9300f/message0.html
> >
> >----------------------
> >This automatic notification message was sent by Sakai Collab
> >(https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a.
> >sakai-dev) site.
> >You can modify how you receive notifications at My Workspace > Preferences.
> >
> >
>
> ----------------------
> This automatic notification message was sent by Sakai Collab
> (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a.
> sakai-dev) site.
> You can modify how you receive notifications at My Workspace > Preferences.
>
----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.
« Return to Thread: Apache configuration.
| Free embeddable forum powered by Nabble | Forum Help |
