True, my reply was from a production point of view. In my opinion, neither mod_webapp or mod_jk2 are production ready, and tomcat 4.1.x is still beta.
If you're looking for a production environment, in my mind that is tomcat 4.0.x (or even 3.3.x), mod_jk, and apache 1.3.x/2.0.39. I see little purpose is automatically working with bleeding-edge components when there is no real way to tell or estimate when those bleeding edge components will be not only released, but released and production ready. What if the components (mod_jk2, tomcat 4.1.x) are 6 months away from production use and your project is only going to take 2 months? You have a 4 month gap. I prefer to match my dev schedule as closely as possible with the availability of production-ready components. For example, my own project is due in 6 weeks. I would love to use tomcat 4.1.x, but there's no way for me to guarantee that 4.1.x will be production ready in 6 weeks. At least not with enough guarantee to satisfy my clients, who refuse to allow beta software into production. Bleeding edge is fine for development, education, experimentation, etc. but sometimes you have to scale back a little and wait for things to settle down. John Turner [EMAIL PROTECTED] -----Original Message----- From: Paul landolt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 16, 2002 10:13 AM To: Tomcat Users List Subject: Re: Apache->Tomcat Howto? Problem with most of the information out there is that it deals with connecting 4.0.x with Apache, not 4.1.x. The Coyote JK2 connector is the preferred method with 4.1.x (jk has be deprecated in favour of jk2). Aside from Andrew Conrad's comments, there seems to be little documentation to be found regarding the topic ...Paul "Turner, John" wrote: > There are really only 2 ways: AJP and WARP. If you want apache to serve > static content, than there is only 1 way at this time, as far as I know: > AJP. > > You will want mod_jk as your connector. You could try mod_jk2, but mod_jk > seems to be the most stable right now. > > Depending on your choice of versions (you will want apache 2.0.39 if you are > going with apache 2), this link might help: > http://www.galatea.com/flashguides/index > > John Turner > [EMAIL PROTECTED] > http://www.aas.com > > -----Original Message----- > From: Chris Ruegger [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 16, 2002 9:07 AM > To: Tomcat Users List > Subject: Apache->Tomcat Howto? > > I want to set up an Apache web server on Red Hat Linux 7.2 > to handle static content and SSL, and forward servlet and JSP > requests to Tomcat 4.0. > > It seems there are about 3 ways to do this: > Http 1.1 > Warp > AJP > > Which approach do most sites use? Can someoneone > point me to the Howto's that describe how I need to configure > Apache and Tomcat to make the Warp approach and > the AJP approaches work? > > Thanks in advance > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
