On 13.07.2009 02:28, Will Glass-Husain wrote: > Thanks Christopher, > > I'll upgrade to the latest mod_jk and look at the timeout params. > We'll see if that helps.
Since you can easily reproduce, it would be a interesting and easy test, to deactivate the tcnative/APR connector and recheck, whether the problem is still there. Then we would at least have an indication where to look for the root cause. There were some fixes between tcnative 1.1.14 and the most recent 1.1.16, but I'm not sure, whether something related was in the list. Regards, Rainer > On Fri, Jul 10, 2009 at 6:05 PM, Christopher > Schultz<ch...@christopherschultz.net> wrote: > Will, > > On 7/6/2009 4:15 PM, Will Glass-Husain wrote: >>>> Interestingly - I can easily reproduce this by repeatedly refreshing >>>> the page when going through httpd >>>> >>>> When I go direct to Tomcat via http, it works fine. >>>> >>>> Maybe it's something about httpd or mod_jk then? > Perhaps. It's been a few days... let's see if Mladen or Rainer are still > reading this thread: they may have some thoughts. My mod_jk experience > is limited to a small-load website that has never really had any problems. > > Higher-throughput sites may require some tuning. I would recommend > (re-)reading the mod_jk documentation for all the settings. Make sure > everything matches properly (timeouts relative to both mod_jk /and/ your > Tomcat connector). > > -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
