On 18 February 2011 20:19, Filip Hanik - Dev Lists <devli...@hanik.com> wrote: > Simplest to try first is the disablereuse flag > http://httpd.apache.org/docs/2.2/mod/mod_proxy.html > disablereuse On > and if that solves the problem, you know that the problem with not enough > threads on tomcat. > (Could be from stale connections that are still holding a thread)
Awesome - that makes it at least 10x more reliable! Still not perfect, but a massive improvement. Any more suggestions on what I can do to clear the last errors & generally how to approach this configuration? (Apache & Tomcat on the same physical server. Load isn't terribly high right now, but I'd like it to be able to scale. There is 2Gb RAM available (although this is shared with PostgreSQL which is tuned to think it has 1024 available for it) Many thanks :) Fran. > Filip > > On 02/18/2011 12:24 PM, Fran Boon wrote: >> >> httpd error log: >> client denied by server configuration: >> proxy:ajp://localhost:8009/geoserver/gwc/service/wms >> >> This happens under 'high' load only: 1st few requests of a batch are >> answered but then they start dying - there are no bad URLs here. >> >> httpd snippet: >> ProxyPreserveHost on >> RewriteRule ^/geoserver/(.*)$ ajp://localhost:8009/geoserver/$1 [P] >> ProxyPassReverse /geoserver ajp://localhost:8009/geoserver/ >> >> <LocationMatch "^(/[\w_]*/geoserver/.*)"> >> Order Allow,Deny >> Allow from all >> </LocationMatch> >> >> I have tried these configuration options without any apparent difference: >> <Proxy ajp://localhost:8009> >> ProxySet keepalive=On timeout=15 ttl=60 >> </Proxy> >> >> Happens even with 'Allow from all' in proxy.conf (in fact nothing in >> that file makes any difference, presumably as it only affects Forward >> proxies. >> >> I have tried with both the default prefork MPM& also the worker MPM. >> >> Back-end is GeoServer in Tomcat 6 (exactly same thing happened with >> 5.5) on Debian Squeeze 64-bit& current Sun JVM. >> Nothing in the logs at the back-end, though, seems to be a problem >> with the Connector. >> Same thing whether or not using the 'APR based Apache Tomcat Native >> library 1.1.20' or not. >> I tried putting in a connectionTimeout into server.xml, but it makes >> no difference: >> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" >> connectionTimeout="60000" /> >> >> Same with setting the minSpareThreads="32" maxThreads="256" >> to match those in apache.conf >> <IfModule mpm_worker_module> >> StartServers 2 >> MaxClients 256 >> MinSpareThreads 32 >> MaxSpareThreads 128 >> ThreadsPerChild 32 >> MaxRequestsPerChild 1024 >> </IfModule> >> >> None of these tuning options seem to make much difference. >> >> Only web posts I've seen are the on/off conditions rather than erratic >> ones. >> >> Many thanks, for any suggestions :) >> >> Fran. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
