search

robbyrob42 / forceworkbench

Automatically exported from code.google.com/p/forceworkbench
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Heroku: server reached MaxClients setting, consider raising the MaxClients setting #568

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Investigate this issue:

2012-03-21T07:17:48+00:00 app[web.2]: [Wed Mar 21 07:17:47 2012] [error] server 
reached MaxClients setting, consider raising the MaxClients setting

Original issue reported on code.google.com by ryan.bra...@gmail.com on 21 Mar 2012 at 7:23

GoogleCodeExporter commented 9 years ago

Original comment by ryan.bra...@gmail.com on 5 Apr 2012 at 6:19

GoogleCodeExporter commented 9 years ago 
FYI, I think this is a 'normal' error message on Heroku, where each web dyno is 
configured with a MaxClients = 1. When Apache starts, it spawns the first 
thread to listen for incoming connections, then logs a warning since it reached 
the MaxClients limit. But this is expected on Heroku. One should scale the 
number of web dynos to increase the concurrency limit of his web app.

Original comment by guillaume.boudreau on 29 Jun 2012 at 1:05

GoogleCodeExporter commented 9 years ago

Original comment by ryan.bra...@gmail.com on 5 Aug 2012 at 5:24

GoogleCodeExporter commented 9 years ago 
Released in 25.0.0

Original comment by ryan.bra...@gmail.com on 10 Aug 2012 at 4:33