Re: Tomcat Site slow and stops responding after certain number of threads
s prasad wrote: We use the JK 2 Connector and for some of the sites we have maxProcessors=75. My understanding is when the maxProcessors limit is reached, the requests are put in queue and this will not cause the site to go down. IS this number dependent on total number of TCP/IP connections hitting that server on port 80? Is there a downfall of bumping this number very high, assuming there is enough memory on the server to allow these threads? Can anyone comment on, how to identify the current connector thread utilization? My experience is that this is not a hard limit, but will be exceeded if the requests at one time go beyond the 75, but those extra threads will be removed when they are done. If you don't mind your java application (tomcat) sharing it's processor time servicing many threads then there shouldn't be any problems. It really depends on how cpu intensive your apps are, more cpu intensive should use fewer threads, imo. -- "Love is mutual self-giving that ends in self-recovery." Fulton Sheen James Black[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Site slow and stops responding after certain number of threads
We use the JK 2 Connector and for some of the sites we have maxProcessors=75. My understanding is when the maxProcessors limit is reached, the requests are put in queue and this will not cause the site to go down. IS this number dependent on total number of TCP/IP connections hitting that server on port 80? Is there a downfall of bumping this number very high, assuming there is enough memory on the server to allow these threads? Can anyone comment on, how to identify the current connector thread utilization? Thanks, Prasad From: Graham Bleach <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Subject: Re: Tomcat Site slow and stops responding after certain number of threads Date: Sat, 3 Apr 2004 12:37:43 +0100 On Thu, Apr 01, 2004 at 10:39:37PM -0500, sp k wrote: > We have a Tomcat site which becomes terribly slow and then stops responding > after the thread count in windows task manager reaches 107 threads. We are > using Tomcat 4.1.27 on windows 2000 machine. Our load tests could never > emulate this behavior that occurs under real load. When the site crashes > the memory consumption of the site is less than the initial max heap size > set for it. > > Did any one ever face similar issues, we are baffled as to why 107 threads? > Is related to the connector threads or JVM's garbage collection? > > Does anyone have any idea why the site would crash at the same thread level? Have you checked the minProcessors and maxProcessors setting for your connector in $CATALINA_HOME/conf/server.xml? You don't say which connector you are using, but the Coyote connectors all have a limit on the number of threads dedicated to connection handling. Documentation on connector configuration: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html It should be logged when you reach the maximum processors, but I can't, offhand remember where. G -- One of my most productive days was throwing away 1000 lines of code. -- Ken Thompson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Free up your inbox with MSN Hotmail Extra Storage! Multiple plans available. http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Site slow and stops responding after certain number of threads
On Thu, Apr 01, 2004 at 10:39:37PM -0500, sp k wrote: > We have a Tomcat site which becomes terribly slow and then stops responding > after the thread count in windows task manager reaches 107 threads. We are > using Tomcat 4.1.27 on windows 2000 machine. Our load tests could never > emulate this behavior that occurs under real load. When the site crashes > the memory consumption of the site is less than the initial max heap size > set for it. > > Did any one ever face similar issues, we are baffled as to why 107 threads? > Is related to the connector threads or JVM's garbage collection? > > Does anyone have any idea why the site would crash at the same thread level? Have you checked the minProcessors and maxProcessors setting for your connector in $CATALINA_HOME/conf/server.xml? You don't say which connector you are using, but the Coyote connectors all have a limit on the number of threads dedicated to connection handling. Documentation on connector configuration: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html It should be logged when you reach the maximum processors, but I can't, offhand remember where. G -- One of my most productive days was throwing away 1000 lines of code. -- Ken Thompson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Site slow and stops responding after certain number of threads
Yes, We have something like this:
Total Memory Allocation: 124
Free Memory: 34
Runtime Max memory: 518
When the site crashes we don't see memory peaks, we only see the thread
count increaase.
From: "STOCKHOLM, Raymond" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Subject: RE: Tomcat Site slow and stops responding after certain number of
threads
Date: Fri, 2 Apr 2004 16:18:20 +0200
Are you sure the JVM has enough memory ?
long totalMemory = Runtime.getRuntime().totalMemory();
long freeMemory = Runtime.getRuntime().freeMemory();
long maxMemory = Runtime.getRuntime().maxMemory();
log.info("totalMemory="+totalMemory);
log.info("freeMemory ="+freeMemory);
log.info("maxMemory ="+maxMemory);
-Message d'origine-
De : s prasad [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 2 avril 2004 15:12
À : [EMAIL PROTECTED]
Objet : Re: Tomcat Site slow and stops responding after certain number
of threads
We have 4 gigs of memory on the box, although the entire machine peaks at
around 2 Gigs we have other sites on the same server running same code that
are perfectly alright. But, when the thread count on a site increases
beyond
the magic number of 107, its slow responding and then a little later it
stops responding.
Prasad
>From: Peter Lin <[EMAIL PROTECTED]>
>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
>To: Tomcat Users List <[EMAIL PROTECTED]>
>Subject: Re: Tomcat Site slow and stops responding after certain number
of
>threads
>Date: Thu, 1 Apr 2004 20:37:30 -0800 (PST)
>
>
>windows by default allocates 1mb of memory per thread.
>107 threads shouldn't cause any problems, unless your
>system only has 128mb of ram. From first hand
>experience, once the allocated memory reach half the
>physical ram, windows starts to disk cache. Once that
>happens, GC performance gets worse. In fact in .NET
>1.0, disk caching causes heap fragmentation and memory
>leaks. If disk cache is kicking in, the performance
>issues may be the result of heap fragmentation, which
>kills GC performance.
>
>peter lin
>
>
>--- sp k <[EMAIL PROTECTED]> wrote:
> > We have a Tomcat site which becomes terribly slow
> > and then stops responding
> > after the thread count in windows task manager
> > reaches 107 threads. We are
> > using Tomcat 4.1.27 on windows 2000 machine. Our
> > load tests could never
> > emulate this behavior that occurs under real load.
> > When the site crashes the
> > memory consumption of the site is less than the
> > initial max heap size set
> > for it.
> >
> > Did any one ever face similar issues, we are baffled
> > as to why 107 threads?
> > Is related to the connector threads or JVM's garbage
> > collection?
> >
> > Does anyone have any idea why the site would crash
> > at the same thread level?
> >
> > Thanks,
> > Prasad
> >
> >
>_
> > Get rid of annoying pop-up ads with the new MSN
> > Toolbar - FREE!
> > http://toolbar.msn.com/go/onm00200414ave/direct/01/
> >
> >
> >
>-
> > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
>
>
>__
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_
Get rid of annoying pop-up ads with the new MSN Toolbar - FREE!
http://toolbar.msn.com/go/onm00200414ave/direct/01/
-
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]
_
FREE pop-up blocking with the new MSN Toolbar get it now!
http://toolbar.msn.com/go/onm00200415ave/direct/01/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Site slow and stops responding after certain number of threads
Are you sure the JVM has enough memory ?
long totalMemory = Runtime.getRuntime().totalMemory();
long freeMemory = Runtime.getRuntime().freeMemory();
long maxMemory = Runtime.getRuntime().maxMemory();
log.info("totalMemory="+totalMemory);
log.info("freeMemory ="+freeMemory);
log.info("maxMemory ="+maxMemory);
-Message d'origine-
De : s prasad [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 2 avril 2004 15:12
À : [EMAIL PROTECTED]
Objet : Re: Tomcat Site slow and stops responding after certain number
of threads
We have 4 gigs of memory on the box, although the entire machine peaks at
around 2 Gigs we have other sites on the same server running same code that
are perfectly alright. But, when the thread count on a site increases beyond
the magic number of 107, its slow responding and then a little later it
stops responding.
Prasad
>From: Peter Lin <[EMAIL PROTECTED]>
>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
>To: Tomcat Users List <[EMAIL PROTECTED]>
>Subject: Re: Tomcat Site slow and stops responding after certain number of
>threads
>Date: Thu, 1 Apr 2004 20:37:30 -0800 (PST)
>
>
>windows by default allocates 1mb of memory per thread.
>107 threads shouldn't cause any problems, unless your
>system only has 128mb of ram. From first hand
>experience, once the allocated memory reach half the
>physical ram, windows starts to disk cache. Once that
>happens, GC performance gets worse. In fact in .NET
>1.0, disk caching causes heap fragmentation and memory
>leaks. If disk cache is kicking in, the performance
>issues may be the result of heap fragmentation, which
>kills GC performance.
>
>peter lin
>
>
>--- sp k <[EMAIL PROTECTED]> wrote:
> > We have a Tomcat site which becomes terribly slow
> > and then stops responding
> > after the thread count in windows task manager
> > reaches 107 threads. We are
> > using Tomcat 4.1.27 on windows 2000 machine. Our
> > load tests could never
> > emulate this behavior that occurs under real load.
> > When the site crashes the
> > memory consumption of the site is less than the
> > initial max heap size set
> > for it.
> >
> > Did any one ever face similar issues, we are baffled
> > as to why 107 threads?
> > Is related to the connector threads or JVM's garbage
> > collection?
> >
> > Does anyone have any idea why the site would crash
> > at the same thread level?
> >
> > Thanks,
> > Prasad
> >
> >
>_
> > Get rid of annoying pop-up ads with the new MSN
> > Toolbar - FREE!
> > http://toolbar.msn.com/go/onm00200414ave/direct/01/
> >
> >
> >
>-
> > To unsubscribe, e-mail:
> > [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
>
>
>__
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_
Get rid of annoying pop-up ads with the new MSN Toolbar - FREE!
http://toolbar.msn.com/go/onm00200414ave/direct/01/
-
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 Site slow and stops responding after certain number of threads
We have 4 gigs of memory on the box, although the entire machine peaks at around 2 Gigs we have other sites on the same server running same code that are perfectly alright. But, when the thread count on a site increases beyond the magic number of 107, its slow responding and then a little later it stops responding. Prasad From: Peter Lin <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Subject: Re: Tomcat Site slow and stops responding after certain number of threads Date: Thu, 1 Apr 2004 20:37:30 -0800 (PST) windows by default allocates 1mb of memory per thread. 107 threads shouldn't cause any problems, unless your system only has 128mb of ram. From first hand experience, once the allocated memory reach half the physical ram, windows starts to disk cache. Once that happens, GC performance gets worse. In fact in .NET 1.0, disk caching causes heap fragmentation and memory leaks. If disk cache is kicking in, the performance issues may be the result of heap fragmentation, which kills GC performance. peter lin --- sp k <[EMAIL PROTECTED]> wrote: > We have a Tomcat site which becomes terribly slow > and then stops responding > after the thread count in windows task manager > reaches 107 threads. We are > using Tomcat 4.1.27 on windows 2000 machine. Our > load tests could never > emulate this behavior that occurs under real load. > When the site crashes the > memory consumption of the site is less than the > initial max heap size set > for it. > > Did any one ever face similar issues, we are baffled > as to why 107 threads? > Is related to the connector threads or JVM's garbage > collection? > > Does anyone have any idea why the site would crash > at the same thread level? > > Thanks, > Prasad > > _ > Get rid of annoying pop-up ads with the new MSN > Toolbar FREE! > http://toolbar.msn.com/go/onm00200414ave/direct/01/ > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Get rid of annoying pop-up ads with the new MSN Toolbar FREE! http://toolbar.msn.com/go/onm00200414ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Site slow and stops responding after certain number of threads
windows by default allocates 1mb of memory per thread. 107 threads shouldn't cause any problems, unless your system only has 128mb of ram. From first hand experience, once the allocated memory reach half the physical ram, windows starts to disk cache. Once that happens, GC performance gets worse. In fact in .NET 1.0, disk caching causes heap fragmentation and memory leaks. If disk cache is kicking in, the performance issues may be the result of heap fragmentation, which kills GC performance. peter lin --- sp k <[EMAIL PROTECTED]> wrote: > We have a Tomcat site which becomes terribly slow > and then stops responding > after the thread count in windows task manager > reaches 107 threads. We are > using Tomcat 4.1.27 on windows 2000 machine. Our > load tests could never > emulate this behavior that occurs under real load. > When the site crashes the > memory consumption of the site is less than the > initial max heap size set > for it. > > Did any one ever face similar issues, we are baffled > as to why 107 threads? > Is related to the connector threads or JVM's garbage > collection? > > Does anyone have any idea why the site would crash > at the same thread level? > > Thanks, > Prasad > > _ > Get rid of annoying pop-up ads with the new MSN > Toolbar FREE! > http://toolbar.msn.com/go/onm00200414ave/direct/01/ > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
