Re: Tomcat 5 slow, it's in production, please help!
Thanks for the advice. I will try your suggestions. I noticed that from the server status view of the tomcat manager, I saw some thread with the status 'S' has the time of '24685295'. Does it mean the thread has hang there for more than 6 hours (close to 7 hours)? --- Parsons Technical Services <[EMAIL PROTECTED]> wrote: > I think that would be the direction I would take. > > If you need more proof: > > Sniff the connection to the server to confirm the > lack of available > connections. So far it is pointing in that > direction. > > Another test you might do is create a connection > from a known IP, close the > browser and monitor the connection status. If it is > hanging open then start > digging. > > I think you may also be experiencing an issue of > clickatosis. It occurs > when the client doesn't think the page is responding > quick enough and since > more is better after 10 or 20 clicks they decide to > wait or give up. Mean > while for each click they cause a request which can > bog things down. > Wrapping this with the held connections you can get > a scenario as such: > > Client hits site. > No or slow response. > Clicks again. Or several times. > Often closes browser and tries over. > This creates a new connection request. > Snowballs from there. > > Think about this, do you really get over a 100k > users in six hours? Or even > 100k page requests? That's a lot of traffic. If the > client machines abandons > the connection before the server, then establishes a > new one, it compound > the problem. > > Find a way to have the OS let Apache handle the > connection timeout and get > it down to a reasonable time. > > Since you are inheriting this, there may be a reason > that the connection > timeout is set so high. If the original creator of > this wanted the user to > be able to sit on a page for a long time without > losing the session and > connection thus causing the user to have to > re-authenticate. But then there > is a trade off. which you are experiencing right > now. > > Get the time down until the complaint about having > to re-login get too high > or until the connection speed delay is acceptable. > > Just my $0.015 > > Doug > - Original Message - > From: "Jeffrey" <[EMAIL PROTECTED]> > To: "Tomcat Users List" > > Sent: Saturday, May 07, 2005 1:05 PM > Subject: Re: Tomcat 5 slow, it's in production, > please help! > > > > It seems that, at least in most cases, the main > menu > > page after a login is loaded slow. After that > other > > pages are loaded pretty quick. Does that mean once > a > > connection is established, browser and server > > communication is ok. If that is the case, maybe I > > should look more at the connection timeout at the > OS > > level (solaris 5.6) since I see a lot of TIME_WAIT > at > > the machine using the 'netstat -n' command. > > > > > > --- Jeffrey <[EMAIL PROTECTED]> wrote: > > > >> Please see the answer embedded below. > >> > >> --- Parsons Technical Services > >> <[EMAIL PROTECTED]> wrote: > >> > >> > 127421 over what period of time? > >> It's about 6 hours. But most of them are at the > >> first > >> hour or so. > >> > > >> > Without a profile it is impossible to say if > >> Tomcat > >> > can handle the load. But > >> > if the memory consumption and the CPU usage is > low > >> > (as noted) it is fairly > >> > safe to say that Tomcat itself is not the > bottle > >> > neck. > >> > > >> > Quick question, why are you using Apache? > >> > >> I am using Apache SSL for SSL connections. It is > the > >> original setup by someone else. > >> > >> > > >> > Also what is the time out for the connection in > >> > Apache? > >> > >> Apache's Timeout value is 300. > MaxKeepAliveRequests > >> is > >> 100 and KeepAliveTimeout is 15 > >> > > >> > Do you get this slow reaction if you are > hitting > >> > Tomcat directly? > >> > >> I did get the slow reaction if I hit Tomcat > directly > >> at port 8080 to the same webapp. But the tomcat > >> manager web pages seem show up fairly quick. > >> > >> > > >> > I may be repeating something that was covered > >> > because I have not been > >> >
Re: Tomcat 5 slow, it's in production, please help!
I think that would be the direction I would take. If you need more proof: Sniff the connection to the server to confirm the lack of available connections. So far it is pointing in that direction. Another test you might do is create a connection from a known IP, close the browser and monitor the connection status. If it is hanging open then start digging. I think you may also be experiencing an issue of clickatosis. It occurs when the client doesn't think the page is responding quick enough and since more is better after 10 or 20 clicks they decide to wait or give up. Mean while for each click they cause a request which can bog things down. Wrapping this with the held connections you can get a scenario as such: Client hits site. No or slow response. Clicks again. Or several times. Often closes browser and tries over. This creates a new connection request. Snowballs from there. Think about this, do you really get over a 100k users in six hours? Or even 100k page requests? That's a lot of traffic. If the client machines abandons the connection before the server, then establishes a new one, it compound the problem. Find a way to have the OS let Apache handle the connection timeout and get it down to a reasonable time. Since you are inheriting this, there may be a reason that the connection timeout is set so high. If the original creator of this wanted the user to be able to sit on a page for a long time without losing the session and connection thus causing the user to have to re-authenticate. But then there is a trade off. which you are experiencing right now. Get the time down until the complaint about having to re-login get too high or until the connection speed delay is acceptable. Just my $0.015 Doug - Original Message - From: "Jeffrey" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Saturday, May 07, 2005 1:05 PM Subject: Re: Tomcat 5 slow, it's in production, please help! It seems that, at least in most cases, the main menu page after a login is loaded slow. After that other pages are loaded pretty quick. Does that mean once a connection is established, browser and server communication is ok. If that is the case, maybe I should look more at the connection timeout at the OS level (solaris 5.6) since I see a lot of TIME_WAIT at the machine using the 'netstat -n' command. --- Jeffrey <[EMAIL PROTECTED]> wrote: Please see the answer embedded below. --- Parsons Technical Services <[EMAIL PROTECTED]> wrote: > 127421 over what period of time? It's about 6 hours. But most of them are at the first hour or so. > > Without a profile it is impossible to say if Tomcat > can handle the load. But > if the memory consumption and the CPU usage is low > (as noted) it is fairly > safe to say that Tomcat itself is not the bottle > neck. > > Quick question, why are you using Apache? I am using Apache SSL for SSL connections. It is the original setup by someone else. > > Also what is the time out for the connection in > Apache? Apache's Timeout value is 300. MaxKeepAliveRequests is 100 and KeepAliveTimeout is 15 > > Do you get this slow reaction if you are hitting > Tomcat directly? I did get the slow reaction if I hit Tomcat directly at port 8080 to the same webapp. But the tomcat manager web pages seem show up fairly quick. > > I may be repeating something that was covered > because I have not been > reading this thread in detail. So sorry if already > asked and answered. > > > Doug > > > > ----- Original Message - > From: "Jeffrey" <[EMAIL PROTECTED]> > To: "Tomcat Users List" > > Sent: Saturday, May 07, 2005 10:44 AM > Subject: Re: Tomcat 5 slow, it's in production, > please help! > > > > This website has many JSP pages of which each has > many > > JSPF included. I wonder whether or not the system > is > > not be able to handle this kind of setting. But > > strange thing is that when we experienced the > > slowness, I looked at the usage of CPU and find > that > > almost 90% of the CPU is idle. > > > > Do anyone know what kind of load a tomcat can > handle. > > I am thinking that maybe a load balancer will > help. > > But I am still puzzled by the fact of low CPU > usage at > > the time of slowness. > > > > From the server status view in tomcat manager, I > can > > see 's Request count: 127421' > > > > --- 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
Re: Tomcat 5 slow, it's in production, please help!
It seems that, at least in most cases, the main menu page after a login is loaded slow. After that other pages are loaded pretty quick. Does that mean once a connection is established, browser and server communication is ok. If that is the case, maybe I should look more at the connection timeout at the OS level (solaris 5.6) since I see a lot of TIME_WAIT at the machine using the 'netstat -n' command. --- Jeffrey <[EMAIL PROTECTED]> wrote: > Please see the answer embedded below. > > --- Parsons Technical Services > <[EMAIL PROTECTED]> wrote: > > > 127421 over what period of time? > It's about 6 hours. But most of them are at the > first > hour or so. > > > > Without a profile it is impossible to say if > Tomcat > > can handle the load. But > > if the memory consumption and the CPU usage is low > > (as noted) it is fairly > > safe to say that Tomcat itself is not the bottle > > neck. > > > > Quick question, why are you using Apache? > > I am using Apache SSL for SSL connections. It is the > original setup by someone else. > > > > > Also what is the time out for the connection in > > Apache? > > Apache's Timeout value is 300. MaxKeepAliveRequests > is > 100 and KeepAliveTimeout is 15 > > > > Do you get this slow reaction if you are hitting > > Tomcat directly? > > I did get the slow reaction if I hit Tomcat directly > at port 8080 to the same webapp. But the tomcat > manager web pages seem show up fairly quick. > > > > > I may be repeating something that was covered > > because I have not been > > reading this thread in detail. So sorry if already > > asked and answered. > > > > > > Doug > > > > > > > > - Original Message - > > From: "Jeffrey" <[EMAIL PROTECTED]> > > To: "Tomcat Users List" > > > > Sent: Saturday, May 07, 2005 10:44 AM > > Subject: Re: Tomcat 5 slow, it's in production, > > please help! > > > > > > > This website has many JSP pages of which each > has > > many > > > JSPF included. I wonder whether or not the > system > > is > > > not be able to handle this kind of setting. But > > > strange thing is that when we experienced the > > > slowness, I looked at the usage of CPU and find > > that > > > almost 90% of the CPU is idle. > > > > > > Do anyone know what kind of load a tomcat can > > handle. > > > I am thinking that maybe a load balancer will > > help. > > > But I am still puzzled by the fact of low CPU > > usage at > > > the time of slowness. > > > > > > From the server status view in tomcat manager, I > > can > > > see 's Request count: 127421' > > > > > > --- 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 th
Re: Tomcat 5 slow, it's in production, please help!
Please see the answer embedded below. --- Parsons Technical Services <[EMAIL PROTECTED]> wrote: > 127421 over what period of time? It's about 6 hours. But most of them are at the first hour or so. > > Without a profile it is impossible to say if Tomcat > can handle the load. But > if the memory consumption and the CPU usage is low > (as noted) it is fairly > safe to say that Tomcat itself is not the bottle > neck. > > Quick question, why are you using Apache? I am using Apache SSL for SSL connections. It is the original setup by someone else. > > Also what is the time out for the connection in > Apache? Apache's Timeout value is 300. MaxKeepAliveRequests is 100 and KeepAliveTimeout is 15 > > Do you get this slow reaction if you are hitting > Tomcat directly? I did get the slow reaction if I hit Tomcat directly at port 8080 to the same webapp. But the tomcat manager web pages seem show up fairly quick. > > I may be repeating something that was covered > because I have not been > reading this thread in detail. So sorry if already > asked and answered. > > > Doug > > > > - Original Message - > From: "Jeffrey" <[EMAIL PROTECTED]> > To: "Tomcat Users List" > > Sent: Saturday, May 07, 2005 10:44 AM > Subject: Re: Tomcat 5 slow, it's in production, > please help! > > > > This website has many JSP pages of which each has > many > > JSPF included. I wonder whether or not the system > is > > not be able to handle this kind of setting. But > > strange thing is that when we experienced the > > slowness, I looked at the usage of CPU and find > that > > almost 90% of the CPU is idle. > > > > Do anyone know what kind of load a tomcat can > handle. > > I am thinking that maybe a load balancer will > help. > > But I am still puzzled by the fact of low CPU > usage at > > the time of slowness. > > > > From the server status view in tomcat manager, I > can > > see 's Request count: 127421' > > > > --- 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] > >> > >> > > > > __ > > 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] > > > > > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 slow, it's in production, please help!
127421 over what period of time? Without a profile it is impossible to say if Tomcat can handle the load. But if the memory consumption and the CPU usage is low (as noted) it is fairly safe to say that Tomcat itself is not the bottle neck. Quick question, why are you using Apache? Also what is the time out for the connection in Apache? Do you get this slow reaction if you are hitting Tomcat directly? I may be repeating something that was covered because I have not been reading this thread in detail. So sorry if already asked and answered. Doug - Original Message - From: "Jeffrey" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Saturday, May 07, 2005 10:44 AM Subject: Re: Tomcat 5 slow, it's in production, please help! This website has many JSP pages of which each has many JSPF included. I wonder whether or not the system is not be able to handle this kind of setting. But strange thing is that when we experienced the slowness, I looked at the usage of CPU and find that almost 90% of the CPU is idle. Do anyone know what kind of load a tomcat can handle. I am thinking that maybe a load balancer will help. But I am still puzzled by the fact of low CPU usage at the time of slowness. From the server status view in tomcat manager, I can see 's Request count: 127421' --- 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] __ 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 slow, it's in production, please help!
This website has many JSP pages of which each has many JSPF included. I wonder whether or not the system is not be able to handle this kind of setting. But strange thing is that when we experienced the slowness, I looked at the usage of CPU and find that almost 90% of the CPU is idle. Do anyone know what kind of load a tomcat can handle. I am thinking that maybe a load balancer will help. But I am still puzzled by the fact of low CPU usage at the time of slowness. >From the server status view in tomcat manager, I can see 's Request count: 127421' --- 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] > > __ 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]
RE: Tomcat 5 slow, it's in production, please help!
As a wild guess Browser drops the connection immediately without notice After 5 minutes, tomcat decides to drop the connection After 30 minutes or so, Solaris finally finishes dropping the connection. Gives a strange meaning to "Keep-Alive" ;) -Original Message- From: Jeffrey [mailto:[EMAIL PROTECTED] Sent: Saturday, May 07, 2005 9:21 AM To: Tomcat Users List Subject: RE: Tomcat 5 slow, it's in production, please help! I am sorry, the box runs a Solaris 5.6 instead of 2.6 as I said before. But still you are probably right, it would be better to get a new OS installed. I didn't use ndd commands to set the TCP parameters. So even though we have the session timeout set to 5 minutes at the tomcat level, that parameter is not honored by the operating system? --- [EMAIL PROTECTED] wrote: > I think some of the problem is at the OS level > > You can set a session time at the tomcat level, but > the default solaris TCP timeouts are hours long. I > hope you used the ndd commands to set the TCP > parameters for short web sessions. > > Also, Solaris 2.6 has a bad thread model and there > are numerous patches required to run it with any > recent Java 2 distributions. To use the 1.4.xxx > JVM would require about a dozen patches. > > It would be way better to try to get Solaris 10 > installed on this box -- It handles the ndd setting > for you and is way faster on the same hardware. > [even solaris 8...] > > > -- Original message > -- > From: <[EMAIL PROTECTED]> > > What does "netstat -nt" show? > > You may have enough connections going that old > ones > > have to time out before you can establish a new > one. > > > > -Original Message- > > From: Jeffrey [mailto:[EMAIL PROTECTED] > > Sent: Friday, May 06, 2005 2:16 PM > > To: tomcat-user@jakarta.apache.org > > Subject: Tomcat 5 slow, it's in production, please > help! > > > > > > 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] > > > > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 slow, it's in production, please help!
I am sorry, the box runs a Solaris 5.6 instead of 2.6 as I said before. But still you are probably right, it would be better to get a new OS installed. I didn't use ndd commands to set the TCP parameters. So even though we have the session timeout set to 5 minutes at the tomcat level, that parameter is not honored by the operating system? --- [EMAIL PROTECTED] wrote: > I think some of the problem is at the OS level > > You can set a session time at the tomcat level, but > the default solaris TCP timeouts are hours long. I > hope you used the ndd commands to set the TCP > parameters for short web sessions. > > Also, Solaris 2.6 has a bad thread model and there > are numerous patches required to run it with any > recent Java 2 distributions. To use the 1.4.xxx > JVM would require about a dozen patches. > > It would be way better to try to get Solaris 10 > installed on this box -- It handles the ndd setting > for you and is way faster on the same hardware. > [even solaris 8...] > > > -- Original message > -- > From: <[EMAIL PROTECTED]> > > What does "netstat -nt" show? > > You may have enough connections going that old > ones > > have to time out before you can establish a new > one. > > > > -Original Message- > > From: Jeffrey [mailto:[EMAIL PROTECTED] > > Sent: Friday, May 06, 2005 2:16 PM > > To: tomcat-user@jakarta.apache.org > > Subject: Tomcat 5 slow, it's in production, please > help! > > > > > > 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] > > > > > > - > 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]
Re: Tomcat 5 slow, it's in production, please help!
Oto Bossert wrote: > Yoo, > > Yes switch to jk2 is faster! But unsupported! Development of mod_jk1.x is going on, but not jk2. I wouldn't advise anyone to select something uncontinued. 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. Check whether you session-timeout is really set correctly. You can set the timeout in the default web.xml for all apps, but you could override it in the webapps web.xml, too. Maybe there it's still set too high. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 slow, it's in production, please help!
Yoo, Yes switch to jk2 is faster! set parameters in OPT_CATALINA with -server Xmx=? and Xms=? Sorry values depend on your available memory on the server, parameters could be different with your version, check or google for correct parameters, should improve performance... Another option could be your code, have a good look at it and try to optimize... Greetings O. On 5/6/05, Jeffrey <[EMAIL PROTECTED]> wrote: > I use just mod_jk, not jk2 I believe. I do have > connectionTimeout="2" 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="2" 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 slow, it's in production, please help!
it sounds like the problem is caused by a large number of connections dying holding things up. peter On 5/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 153 ESTABLISHED connections to port 443 > 553 connections to port 443 in the process of dying. > 1420 connections total (Assuming I'm reading the output of wc correctly;) > > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep ESTABLISHED|wc > 6934851 55442 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep CLOSE_WAIT|wc > 101 7077980 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep TIME_WAIT|wc > 6104270 47590 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep FIN_WAIT|wc > 3 21 237 > [EMAIL PROTECTED] tony]$ cat netstat.txt |wc >14209929 112098 > > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 127.0.0.1.8009|grep > ESTABLISHED|wc > 5123584 40960 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 127.0.0.1.8009|grep WAIT|wc > 25 1751950 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 129.93.1.146.443|grep WAIT|wc > 5533871 43222 > [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 129.93.1.146.443|grep > ESTABLISHED|wc > 1531071 12242 > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, May 06, 2005 7:00 PM > To: Tomcat Users List; [EMAIL PROTECTED] > Subject: RE: Tomcat 5 slow, it's in production, please help! > > I think some of the problem is at the OS level > > You can set a session time at the tomcat level, but the default solaris TCP > timeouts are hours long. I hope you used the ndd commands to set the TCP > parameters for short web sessions. > > Also, Solaris 2.6 has a bad thread model and there are numerous patches > required to run it with any recent Java 2 distributions. To use the > 1.4.xxx JVM would require about a dozen patches. > > It would be way better to try to get Solaris 10 installed on this box -- It > handles the ndd setting for you and is way faster on the same hardware. > [even solaris 8...] > > -- Original message -- > From: <[EMAIL PROTECTED]> > > What does "netstat -nt" show? > > You may have enough connections going that old ones > > have to time out before you can establish a new one. > > > > -Original Message- > > From: Jeffrey [mailto:[EMAIL PROTECTED] > > Sent: Friday, May 06, 2005 2:16 PM > > To: tomcat-user@jakarta.apache.org > > Subject: Tomcat 5 slow, it's in production, please help! > > > > > > 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 > > > > --
RE: Tomcat 5 slow, it's in production, please help!
153 ESTABLISHED connections to port 443 553 connections to port 443 in the process of dying. 1420 connections total (Assuming I'm reading the output of wc correctly;) [EMAIL PROTECTED] tony]$ cat netstat.txt |grep ESTABLISHED|wc 6934851 55442 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep CLOSE_WAIT|wc 101 7077980 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep TIME_WAIT|wc 6104270 47590 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep FIN_WAIT|wc 3 21 237 [EMAIL PROTECTED] tony]$ cat netstat.txt |wc 14209929 112098 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 127.0.0.1.8009|grep ESTABLISHED|wc 5123584 40960 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 127.0.0.1.8009|grep WAIT|wc 25 1751950 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 129.93.1.146.443|grep WAIT|wc 5533871 43222 [EMAIL PROTECTED] tony]$ cat netstat.txt |grep 129.93.1.146.443|grep ESTABLISHED|wc 1531071 12242 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 06, 2005 7:00 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Tomcat 5 slow, it's in production, please help! I think some of the problem is at the OS level You can set a session time at the tomcat level, but the default solaris TCP timeouts are hours long. I hope you used the ndd commands to set the TCP parameters for short web sessions. Also, Solaris 2.6 has a bad thread model and there are numerous patches required to run it with any recent Java 2 distributions. To use the 1.4.xxx JVM would require about a dozen patches. It would be way better to try to get Solaris 10 installed on this box -- It handles the ndd setting for you and is way faster on the same hardware. [even solaris 8...] -- Original message -- From: <[EMAIL PROTECTED]> > What does "netstat -nt" show? > You may have enough connections going that old ones > have to time out before you can establish a new one. > > -Original Message- > From: Jeffrey [mailto:[EMAIL PROTECTED] > Sent: Friday, May 06, 2005 2:16 PM > To: tomcat-user@jakarta.apache.org > Subject: Tomcat 5 slow, it's in production, please help! > > > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 slow, it's in production, please help!
I think some of the problem is at the OS level You can set a session time at the tomcat level, but the default solaris TCP timeouts are hours long. I hope you used the ndd commands to set the TCP parameters for short web sessions. Also, Solaris 2.6 has a bad thread model and there are numerous patches required to run it with any recent Java 2 distributions. To use the 1.4.xxx JVM would require about a dozen patches. It would be way better to try to get Solaris 10 installed on this box -- It handles the ndd setting for you and is way faster on the same hardware. [even solaris 8...] -- Original message -- From: <[EMAIL PROTECTED]> > What does "netstat -nt" show? > You may have enough connections going that old ones > have to time out before you can establish a new one. > > -Original Message- > From: Jeffrey [mailto:[EMAIL PROTECTED] > Sent: Friday, May 06, 2005 2:16 PM > To: tomcat-user@jakarta.apache.org > Subject: Tomcat 5 slow, it's in production, please help! > > > 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] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 slow, it's in production, please help!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, May 06, 2005 3:39 PM To: Jeffrey; Tomcat Users List Subject: RE: Tomcat 5 slow, it's in production, please help! There are certainly people here who understand this much better than I, but ESTABLISHED these connections are doing something or are capable of doing something TIME WAIT these connections are in the process of dying CLOSE WAIT FIN WAIT 2 They can't do anything useful but do occupy space until they are finally gone. If the browser just goes away and doesn't end the connection, the server has to wait for a while before ending it and waiting for responses that never come. -Original Message- From: Jeffrey [mailto:[EMAIL PROTECTED] Sent: Friday, May 06, 2005 3:10 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Tomcat 5 slow, it's in production, please help! Thanks for reply. With "netstat -n", I got numerous records. Please see the attached file if the following is hard to see. TCP Local AddressRemote AddressSwind Send-Q Rwind Recv-Q State - -- - -- --- 129.93.1.146.33544 129.93.1.146.12002 32768 0 32768 0 CLOSE_WAIT 129.93.1.146.33572 129.93.1.146.12002 32768 0 32768 0 CLOSE_WAIT 129.93.1.146.33573 129.93.1.146.12002 32768 0 32768 0 CLOSE_WAIT 127.0.0.1.33692 127.0.0.1.8009 32768 0 32768 0 ESTABLISHED 127.0.0.1.8009 127.0.0.1.33692 32768 0 32768 0 ESTABLISHED 127.0.0.1.33694 127.0.0.1.8009 32768 0 32768 0 ESTABLISHED 127.0.0.1.8009 127.0.0.1.33694 32768 0 32768 0 ESTABLISHED 127.0.0.1.33710 127.0.0.1.8009 32768 0 32768 0 ESTABLISHED [snip] too much stuff [snip] 129.93.1.146.443 164.119.68.37.2826 64186 0 8760 0 TIME_WAIT 129.93.1.146.443 24.27.148.239.2308 16365 0 8760 0 ESTABLISHED 129.93.1.146.443 164.119.68.37.2919 65535 0 8658 0 ESTABLISHED 129.93.1.146.36485 64.89.177.72.5 64677 0 9660 0 TIME_WAIT 127.0.0.1.8007 127.0.0.1.36488 32768 0 32768 0 TIME_WAIT 129.93.1.146.36487 64.89.177.72.5 64677 0 9660 0 TIME_WAIT 129.93.1.146.443 65.31.230.130.1206 11368 0 8760 0 FIN_WAIT_2 129.93.1.146.443 65.31.230.12.60763 17520 1087 8760 0 ESTABLISHED 129.93.1.146.443 129.93.120.170.1460 17520 0 8658 0 ESTABLISHED 129.93.1.146.36489 64.89.177.72.5 64677 0 9660 0 TIME_WAIT 127.0.0.1.36336 127.0.0.1.8009 32768 0 32768 0 TIME_WAIT 129.93.1.146.443 24.252.59.10.392316365 0 8760 0 ESTABLISHED 129.93.1.146.443 69.20.197.189.11999112 0 9016 0 ESTABLISHED 127.0.0.1.36491 127.0.0.1.8009 32768 0 32768 0 ESTABLISHED 127.0.0.1.8009 127.0.0.1.36491 32768 0 32768 0 ESTABLISHED 129.93.1.146.443 24.208.93.36.955425200 0 8682 0 ESTABLISHED --- [EMAIL PROTECTED] wrote: > What does "netstat -nt" show? > You may have enough connections going that old ones > have to time out before you can establish a new one. > > -Original Message- > From: Jeffrey [mailto:[EMAIL PROTECTED] > Sent: Friday, May 06, 2005 2:16 PM > To: tomcat-user@jakarta.apache.org > Subject: Tomcat 5 slow, it's in production, please > help! > > > 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 minut
Re: Tomcat 5 slow, it's in production, please help!
I use just mod_jk, not jk2 I believe. I do have connectionTimeout="2" 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="2" 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]
Re: Tomcat 5 slow, it's in production, please help!
I actually have the reloadable set to true for my webapps. I will change it to false. Thanks for the remind. What optimal java parameters in your mind are important ? Thanks for taking look at this. --- Oto Bossert <[EMAIL PROTECTED]> wrote: > Yoo, > > Probably you already looked at it but : > > 1) Make sure not to use reloadable in context > descriptions. > 2) Start tomcat with optimal java parameters, > concerning memory heap and stack > 3) Make sure that connections to database are > minimal, do requery if > answer is always the > same... > > Good luck, > > Greetings O. > > 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] > > Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 slow, it's in production, please help!
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="2" 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]
Re: Tomcat 5 slow, it's in production, please help!
Yoo, Sorry bas typo, in 3) I meant, do NOT requery ;) Greetings O. On 5/6/05, Oto Bossert <[EMAIL PROTECTED]> wrote: > Yoo, > > Probably you already looked at it but : > > 1) Make sure not to use reloadable in context descriptions. > 2) Start tomcat with optimal java parameters, concerning memory heap and stack > 3) Make sure that connections to database are minimal, do requery if > answer is always the > same... > > Good luck, > > Greetings O. > > 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]
Re: Tomcat 5 slow, it's in production, please help!
Yoo, Probably you already looked at it but : 1) Make sure not to use reloadable in context descriptions. 2) Start tomcat with optimal java parameters, concerning memory heap and stack 3) Make sure that connections to database are minimal, do requery if answer is always the same... Good luck, Greetings O. 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]
RE: Tomcat 5 slow, it's in production, please help!
What does "netstat -nt" show? You may have enough connections going that old ones have to time out before you can establish a new one. -Original Message- From: Jeffrey [mailto:[EMAIL PROTECTED] Sent: Friday, May 06, 2005 2:16 PM To: tomcat-user@jakarta.apache.org Subject: Tomcat 5 slow, it's in production, please help! 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]
Tomcat 5 slow, it's in production, please help!
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]
