Cool, it is starting to make a bit more sense. Does that mean that setting settings in apache:/etc/httpd/conf/workers.properties will override any workers.properties set in tomcat servers?
> -----Original Message----- > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Sent: 24 August 2007 15:10 > To: Tomcat Users List > Subject: Re: workers.properties confusion > > [EMAIL PROTECTED] wrote: > > However I am a bit confused between the > > /etc/httpd/conf/workers.properties for apache and > > /usr/share/tomcat/conf/workers.properties > > You only need one workers.properties file: it configures > mod_jk for connections to the various Tomcat instances you > want to use. > > > Another potential issue is that we are using apache > prefork. From what > > I have googled so far it looks like apache mpm would be > better for us. > > We typically have one apache box sitting in front of 12 tomcats. > > Prefork works just fine with mod_jk. IIRC, mpm does /not/ > work well with mod_jk (or maybe you just have to be careful?). > One less thing to worry about then for now. Only reason I thought it might be an issue was because some web pages suggest mpm scales better, and works better on multi cpu systems. Regards ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
