Re: [users@httpd] Apache Crashing Everyday

Depending on your version of Tomcat it might be better to move to using mod_proxy_ajp or even switching to Tomcat's http listener and talking HTTP. > On Mar 2, 2017, at 1:55 AM, Jayaram Ponnusamy > wrote: > > Hi Jim & Jason, > > Yes We are planning to upgrade to httpd 2.4.25 (Stable Version).

Re: [users@httpd] Apache Crashing Everyday

Hi Jim & Jason, Yes We are planning to upgrade to httpd 2.4.25 (Stable Version). So, in the 2.4.25 also we should use mod_jk to connect with Tomcat or anyother better options are there? Tomcat instances are running on different machines. And mod_php is not configured. Thanks On Wed, Mar 1, 2017

Re: [users@httpd] Apache Crashing Everyday

Hello, You will also need to turn off mod_php if it’s loaded. —jason Jason BrooksSystems Administrator eROIPerformance is Art. m: 505 nw couch #300 w: eroi.com t: 503.290.3105f: 503.228.4249 fb: fb.com/eROI

Re: [users@httpd] Apache Crashing Everyday

If you can, I would upgrade to httpd 2.4.x... If you must stay w/ 2.2.x, then Worker might be more reliable for you than Event. > On Mar 1, 2017, at 9:56 AM, Jayaram Ponnusamy > wrote: > > Thanks Jim for the suggestion. > I will update > Timeout 5 > KeepAliveTimeout 2 > > We are using Apache 2

Re: [users@httpd] Apache Crashing Everyday

Thanks Jim for the suggestion. I will update Timeout 5 KeepAliveTimeout 2 We are using Apache 2.2.23 We will try to install Event MPM and will check. Thanks Jay On Mar 1, 2017 5:05 PM, "Jim Jagielski" wrote: You should not be using prefork unless you really, really need to. Assuming you are

Re: [users@httpd] Apache Crashing Everyday

You should not be using prefork unless you really, really need to. Assuming you are running 2.4.x, I would strongly suggest running the Event MPM. Your Timeout and KeepAliveTimeout values are also way too big; I'd recommend 5 and 2, respectively. > On Mar 1, 2017, at 4:19 AM, Jayaram Ponnusamy

[users@httpd] Apache Crashing Everyday

Dear All, We are using 2 Apache & 2 Tomcat with LoadBalance. Everyday the site is goes down and restarting Apache & Tomcat only help to bring the site back. I could see below errors on WebServer's Error Log, when the "total children" count increased more than 200 then Apache is not responding. I