I use just mod_jk, not jk2 I believe. I do have connectionTimeout="20000" set to AJP connector in server.xml
Is there any performance issues with jk? Should I switch to jk2? Thanks. --- e <[EMAIL PROTECTED]> wrote: > What JK version do you use? To quote Mladen: > > "You are probably using prefork mpm, so there is no > way to > control the number of connections to Tomcat in any > way, trough > mod_jk. You can limit it only by setting MaxClients > in the httpd.conf > to the maximum number desired. > Because of pre-forking mechanism each child process > will eventually > establish a single connection to Tomcat, thus the > number of connections > will rise from StartServers to MaxClients. > > So there are two solutions for prefork. > 1. Make maxThreads==MaxClients > 2. Add connectionTimeout="20000" to AJP connector." > > On 5/6/05, Jeffrey <[EMAIL PROTECTED]> wrote: > > I have a apache/tomcat environment that has some > > problems recently. The environment has the > following: > > 1. Apache 1.3 > > 2. Tomcat 5.0.28 (Max memory 384mb) > > 3. JDK 1.4.2_06 > > > > My apache has MaxClient set to 256 (apache > default). > > The maxThread for tomcat is 500. The site is a > > database driven site. > > > > It seems working fine when load is low. But when > there > > are more than 150 threads (from the sever status > view > > of the tomcat manager), it's response time is very > > slow (5 - 10 minutes). I have tested the database > > connections, they seem responding fairly well. > > > > Interesting thing is that most of time the slow > > response time only happens when a user login. Once > the > > user login and get the main menu page, the user > will > > get a good response time. Is it related to > KeepAlive > > connections. > > > > Another strange thing is that many threads always > show > > up in the server status view on the tomcat html > > manager page even though I am sure the request has > > gone (I tested this by making a request, then > close > > the browser). > > > > My CPU usage is low when the slowdown is > experienced > > (Using the top command on this solaris box which > has > > old solaris operating system 2.6? with 1GB memory. > > > > I set the session timeout time to 5 minutes, but > in > > the session view of tomcat manager, I see message > "30 > > - <40 minutes:136 sessions". How a session that is > > more than 30 minutes is still there. Maybe I don't > > understand this message correctly. > > > > Please advice. This is a production machine. Helps > are > > greatly appreciated. > > > > Thanks. > > > > Jeffrey. > > > > Discover Yahoo! > > Get on-the-go sports scores, stock quotes, news > and more. Check it out! > > http://discover.yahoo.com/mobile.html > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
