I think I've got to the bottom of this. You must make sure the tomcat AJP1.3 connector has at least the same number of processors (MaxProcessors) as are defined in apache httd.conf (MaxClients). Each apache process grabs an ajp1.3 processor and holds it for it's lifetime, at which point tomcat recycles it.
This is an issue you'd probably only see on a busy site or in load testing. Hope this helps somebody. N. Quoting NickL <[EMAIL PROTECTED]>: > > Config: Tomcat 4.0.6, Apache 1.3.27, JK1.2 > After a while (~100 requests) you get mostly Internal Server Errors when > > accessing the service through apache. However, accessing Tomcat directly > on > 8080 works fine still. > > Does anyone have any ideas why this is and how to fix it? It's as if > tomcat > runs out of processors. There are 'no processor available' messages in > the > catalina log also. > > workers.properties defines a single tomcat instance that is used by all > virtual > sites. > > Cheers for any ideas, > > Nick. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > ElementFour.net 0709 222 JAVA 0709 222 (5282) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
