By default, the WARP connector, and Tomcat-Apache service are commented out.
They are included as examples if you want to use them, but the default connector is the Coyote/JK2 connector. My suggestion would be to use JK or JK2 to connect Apache and Tomcat. It is a reasonably well documented process (compared to other connectors) and there are a lot of examples available. The other easy alternative is to change the connector for HTTP/1.1 from port 8080 to port 80, and only use Tomcat. -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Friday, 11 October 2002 11:24 To: Tomcat Users List Subject: Re: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache Server?) On Thu, 10 Oct 2002, Mark R. Diggory wrote: > Date: Thu, 10 Oct 2002 18:13:17 -0400 > From: Mark R. Diggory <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: mod_webapp (was: Re: TOMCAT-STANDALONE needed with Apache > Server?) > > Hi all, > > This is a little confusing, I notice that in 4.1's server.xml file it > still has the WARP connector as the "default" example of connecting up > to apache. If what you say is the case, should this be mod_jk instead? > i.e. Shouldn't this be a more appropriate connector example that works > on both Windows and other platforms, expecially if mod_webapp is dead? There is also a mod_jk connector in the default configuration (on port 8009). The difference is that jk doesn't require a custom service/engine/context hierarchy -- it uses the standard one. > > Cheers, > -Mark Craig -- 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]>
