Re: Websocket semaphore lock on close() blocks all tomcat threads

On 14/07/2020 21:08, Mark Thomas wrote: > On 14/07/2020 20:57, Sridhar Rao wrote: >> >> We notice a behavior with tomcat where it becomes unresponsive and all >> http threads go into a timed wait state and the node becomes unresponsive. >> >> Tomcat Version: 8.5.47 > > > >> Could this be a

Re: Websocket semaphore lock on close() blocks all tomcat threads

On 14/07/2020 20:57, Sridhar Rao wrote: > > We notice a behavior with tomcat where it becomes unresponsive and all > http threads go into a timed wait state and the node becomes unresponsive. > > Tomcat Version: 8.5.47 > Could this be a tomcat defect? Possibly. Let me take a look. I don't

TCP connection vs Tomcat threads vs File Descriptors - please help

Hi All, can someone please help in understand  that how TCP connections are interlinked with the no. ofFile Descriptors & no of threads configured over a machine . Setup details :OD - Centos 6Tomcat7Java 7 Recently i have faced an problem in while my application was having +20k TCP connections

Re: TCP connection vs Tomcat threads vs File Descriptors - please help

Am 17.10.2015 um 08:27 schrieb vicky: Hi All, can someone please help in understand that how TCP connections are interlinked with the no. ofFile Descriptors & no of threads configured over a machine . Setup details :OD - Centos 6Tomcat7Java 7 Recently i have faced an problem in while my

Re: TCP connection vs Tomcat threads vs File Descriptors - please help

Thank you so much Rainer, for sparing time & answering my query. Vicky On Saturday, 17 October 2015 5:17 PM, Rainer Jung wrote: Am 17.10.2015 um 08:27 schrieb vicky: > Hi All, > can someone please help in understand  that how TCP connections are >

Re: Tomcat threads dependency on net.core.somaxconn value on Linux

compression=on compressableMimeType=text/html, text/xml xpoweredBy=false server=false / Any inputs regarding the Tomcat threads and Linux net.core.somaxconn will be greatly appreciated to support many concurrent connections. If you use acceptCount=5, Tomcat will ask for that socket queue

Re: Tomcat threads dependency on net.core.somaxconn value on Linux

enableLookups=false keepAliveTimeout=30 maxKeepAliveRequests=1 acceptCount=5 socketBuffer=10240 executor=tomcatThreadPool compression=on compressableMimeType=text/html, text/xml xpoweredBy=false server=false / Any inputs regarding the Tomcat threads and Linux net.core.somaxconn

Tomcat threads dependency on net.core.somaxconn value on Linux

socketBuffer=10240 executor=tomcatThreadPool compression=on compressableMimeType=text/html, text/xml xpoweredBy=false server=false / Any inputs regarding the Tomcat threads and Linux net.core.somaxconn will be greatly appreciated to support many concurrent

Re: Running native JNI calls in parallel from different Tomcat threads

though I am getting web requests in parallel, the native calls seem to be serialized. I don't take any locks in the native code that would force serialization. Is there anything in Tomcat that prevents same native calls being called in parallel from separate Tomcat threads? Seems unlikely

Running native JNI calls in parallel from different Tomcat threads

to be serialized. I don't take any locks in the native code that would force serialization. Is there anything in Tomcat that prevents same native calls being called in parallel from separate Tomcat threads? Thanks, Jas

Tomcat Threads busy

Hi when a request comes to tomcat and tomcat does not have any free thread available or all the threads are busy and request queue is also full then where I need to write the logic for redirect the request to some other server. I have ConnectionRedirectionValve.java already written but in that

Re: Tomcat Threads busy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Anil, On 7/23/13 4:35 AM, Anil Goyal -X (anigoyal - ARICENT TECHNOLOGIES MAURIITIUS LIMITED at Cisco) wrote: That logic needs to happen in another layer, in a load-balancer. Tomcat cannot do this on its own. - -chris -BEGIN PGP

Tomcat threads management

Hi. versions : Front-end httpd : [Mon Apr 25 19:13:18 2011] [notice] Apache/2.2.9 (Debian) DAV/2 mod_jk/1.2.26 mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations Tomcat: Using CATALINA_BASE: /usr/share/tomcat5.5 Using CATALINA_HOME:

Re: Tomcat threads management

2011/4/29 André Warnier a...@ice-sa.com: Server version: Apache Tomcat/5.5 Server built: Oct 15 2008 12:57:44 Server number: 5.5.26.0 Intuitively, I would expect that after some time, the number of live threads would be decreasing back to the minSpareThreads value, but that does not seem

AW: Restarting Tomcat Threads

Darmstadt Geschäftsführer: Detlev Homilius, Thomas Strauß -Ursprüngliche Nachricht- Von: David kerber [mailto:dcker...@verizon.net] Gesendet: Dienstag, 19. April 2011 17:02 An: Tomcat Users List Betreff: Re: Restarting Tomcat Threads On 4/19/2011 10:34 AM, Zbynek Vavros wrote

Restarting Tomcat Threads

Hi, I would like to ask on strange behavior Im experiencing. I have webapp that connects to Lotus Notes periodically(every 1 minute). For this I have class that implements Runnable that takes care about connection itself. Im starting this using basic : Thread t = new

RE: Restarting Tomcat Threads

From: Zbynek Vavros [mailto:zbynek_vav...@cz.ibm.com] Subject: Restarting Tomcat Threads I have noticed that when I kill Tomcat (shut down its service) How do you kill Tomcat? (Be specific.) then after start this thread is started automatically (I can see messages about connecting

RE: Restarting Tomcat Threads

| --| | | Subject: | | --| |RE: Restarting Tomcat Threads

Re: Restarting Tomcat Threads

Zbynek Vavros wrote: - How do you kill Tomcat ? I stop its service. - You say after start and I didnt [sic] start anything in the same sentence; you're contradicting yourself. I start Tomcat which starts my webapp but connection to Lotus is started separatedlly. = I start my webapp but do not

Re: Restarting Tomcat Threads

: | | --| |RE: Restarting Tomcat Threads

RE: Tomcat threads

@gmail.com] Sent: Tuesday, March 02, 2010 6:43 PM To: Tomcat Users List Subject: Re: Tomcat threads Why is it illlogical? Fast is a relative term. If the number of requests increases, the number of threads that can be handled by the system goes down . The context switches and the pain to handle

Re: Tomcat threads

chuck.caldar...@unisys.com wrote: From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads Why is it illlogical? 40+ years of system architecture experience. If the number of requests increases, the number of threads that can be handled by the system goes

Re: Tomcat threads

On 03/03/2010 17:21, Bharath Vasudevan wrote: Hi Charles, Let me explain the scenario. When tomcat gets a request, it does a socket send to some other process to handle the request and then respond. This would happen fast. But assuming 20k client requests come in at the same time, the

Re: Tomcat threads

: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads If we get a request on a thread, let some other thread do the work for it and store the response info. The thread which does the work writes the response on that request. If the processing is fast, why would you go

Re: Tomcat threads

That would be the last go. Trying to figure out if there is techniques to handle such scenarios. Looks like comet can asynchronously push data to the user. If this is going to be seamless to the client, it might as well look like a response for their request. On Wed, Mar 3, 2010 at 9:25 AM, Mark

RE: Tomcat threads

From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads When tomcat gets a request, it does a socket send to some other process to handle the request and then respond. Tomcat doesn't do that - your webapp does. You have now introduced a previously unmentioned

RE: Tomcat threads

From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads Looks like comet can asynchronously push data to the user. You do understand that there really is no such thing as push (at least in HTTP)? The client has to have a receive up, so you can't use just a plain

Re: Tomcat threads

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bharath, On 3/2/2010 7:42 PM, Bharath Vasudevan wrote: Why is it illlogical? Fast is a relative term. If the number of requests increases, the number of threads that can be handled by the system goes down . The context switches and the pain to

Re: Tomcat threads

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bharath, On 3/3/2010 12:21 PM, Bharath Vasudevan wrote: Let me explain the scenario. When tomcat gets a request, it does a socket send to some other process to handle the request and then respond. This would happen fast. But assuming 20k client

Re: Tomcat threads

[mailto:bharath@gmail.com] Subject: Re: Tomcat threads When tomcat gets a request, it does a socket send to some other process to handle the request and then respond. Tomcat doesn't do that - your webapp does. You have now introduced a previously unmentioned dependency

Re: Tomcat threads

On 3 March 2010 18:24, Bharath Vasudevan bharath@gmail.com wrote: Hmmm... No, the server will allocate maxThreads request handlers; the other requests would sit in the TCP stack's queue (not in the JVM), up to the configured acceptCount value - which you can set as high as your OS

Re: Tomcat threads

Thanks Folks. On Wed, Mar 3, 2010 at 1:03 PM, Peter Crowther peter.crowt...@melandra.comwrote: On 3 March 2010 18:24, Bharath Vasudevan bharath@gmail.com wrote: Hmmm... No, the server will allocate maxThreads request handlers; the other requests would sit in the TCP stack's queue

Tomcat threads

Hi, I would like to know more on the threads created in tomcat. Are they user level threads or kernel threads? I see that the requests are kicked off through the threads from a pool (which has a configured size), how can this be scalable? Also, from my understanding in servlets, the response

RE: Tomcat threads

From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Tomcat threads Are they user level threads or kernel threads? Depends on the particular JVM being used, not on Tomcat. Pretty much all modern JVMs use a kernel thread for each java.lang.Thread instance on which start() has

Re: Tomcat threads

. The thread which does the work writes the response on that request. Regards, Bharath On Tue, Mar 2, 2010 at 3:57 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Tomcat threads Are they user level threads or kernel threads

RE: Tomcat threads

From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads If we get a request on a thread, let some other thread do the work for it and store the response info. The thread which does the work writes the response on that request. If the processing is fast, why

Re: Tomcat threads

at 4:34 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads If we get a request on a thread, let some other thread do the work for it and store the response info. The thread which does the work

Re: Tomcat threads

Caldarale, Charles R chuck.caldar...@unisys.com wrote in message news:99c8b2929b39c24493377ac7a121e21f96cb817...@usea-exch8.na.uis.unisys.com... From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads If we get a request on a thread, let some other thread do

RE: Tomcat threads

From: Bharath Vasudevan [mailto:bharath@gmail.com] Subject: Re: Tomcat threads Why is it illlogical? 40+ years of system architecture experience. If the number of requests increases, the number of threads that can be handled by the system goes down. You'll have to explain that one

RE: Tomcat threads

From: Bill Barker [mailto:billwbar...@verizon.net] Subject: Re: Tomcat threads basically the request is handed off to another thread and the original one returns to the pool. This also allows for two-way communication instead of relying on polling. What's required on the client end? You

Re: Tomcat threads

Caldarale, Charles R chuck.caldar...@unisys.com wrote in message news:99c8b2929b39c24493377ac7a121e21f96cb817...@usea-exch8.na.uis.unisys.com... From: Bill Barker [mailto:billwbar...@verizon.net] Subject: Re: Tomcat threads basically the request is handed off to another thread

RE: Tomcat threads

From: Bill Barker [mailto:billwbar...@verizon.net] Subject: Re: Tomcat threads The examples in Tomcat 7 are mostly server-push (e.g. fake stock ticker, chat). These are done by not completing the connection, and just pumping more data to a chunked response (so you get the spinning wheel

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Pid wrote: I am not a number! That betrays your age too, you know that ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

On 22.05.2009 03:54, Pantvaidya, Vishwajit wrote: -Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Thursday, May 21, 2009 3:37 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

? Are you just offended by the number of threads, or do you have a legitimate resource problem? But mod_jk does not like tomcat threads timing out and logs the message increase the backend idle connection timeout or the connection_pool_minsize in the mod_jk logs which leads me to believe that its

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Friday, May 22, 2009 8:37:52 AM Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chetan, On 5/21/2009 2:08

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Chetan Chheda [mailto:chetan_chh...@yahoo.com] Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity As with Vishwajit, my tomcat ends up with all threads busy and not serving any new requests. After setting the connectionTimeout

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Friday, May 22, 2009 2:53 AM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity My point is: persistent connections are good

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity [Pantvaidya, Vishwajit] Why are connections idle for a long time not good? He didn't say they weren't good, he said they weren't

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

On 22.05.2009 21:09, Pantvaidya, Vishwajit wrote: -Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Friday, May 22, 2009 2:53 AM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity My

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Friday, May 22, 2009 12:39 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity [Pantvaidya, Vishwajit] Why are connections idle

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Caldarale, Charles R wrote: From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity if you add -p to netstat (at least under Linux), it will also show the program that corresponds to that line

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: Pid [mailto:p...@pidster.com] Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity I am not a number! But are you a free man? We want information, by hook or by crook... (Apologies to the late Patrick McGoohan.) - Chuck

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Trying to add some info below. On 21.05.2009 05:09, Caldarale, Charles R wrote: From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity So socket_keepalive is already 1. So does this mean

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vishwajit, On 5/19/2009 6:08 PM, Pantvaidya, Vishwajit wrote: No, Tomcat uses precisely 1 thread to handle each incoming HTTP request. If keepalives are used, multiple requests may be handled by the same thread before it is returned to the pool,

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vishwajit, On 5/20/2009 3:01 PM, Pantvaidya, Vishwajit wrote: [Pantvaidya, Vishwajit] Ok so RUNNABLE i.e. persistent threads should not be an issue. The only reason why I thought that was an issue was that I was observing that the none of the

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

I am following this thread with great interest. I have a similar issue as Vishwajit and have resorted to adding the connectionTimeout to get rid of a large number of RUNNABLE threads. But mod_jk does not like tomcat threads timing out and logs the message increase the backend idle connection

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

1) If you want to analyze your original problem, you need to get back to the original situation, i.e. without connectionTimeout. It doesn't make much sense to guess about the original problem by looking at something very different. [Pantvaidya, Vishwajit] Yes - I have already initiated

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

On 21.05.2009 20:59, Pantvaidya, Vishwajit wrote: 3) I think I already indicated that you do not want to look at entries in TIME_WAIT state. This state is special and not related to any threads [Pantvaidya, Vishwajit] My netstat o/p had FIN_WAIT and CLOSE_WAIT, but not TIMED_WAIT. Did some

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, May 21, 2009 10:05 AM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Vishwajit, On 5/20/2009 3:01

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

On 22.05.2009 00:19, Pantvaidya, Vishwajit wrote: [Pantvaidya, Vishwajit] I will set - cachesize=1 (doc says jk will autoset this value only for worker-mpm and we use httpd 2.0 prefork) You don't have to: JK will discover this number for the Apache web server automatically and set the pool

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Thursday, May 21, 2009 3:37 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity On 22.05.2009 00:19, Pantvaidya, Vishwajit wrote

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Subject: RE: Running out of tomcat threads - why many threads inRUNNABLEstage even with no activity - Setting connectionTimeout in server.xml seems to have resolved the issue Only because you're throwing away what appears

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

of threads. I certainly don't mind if the TP-Processor threads continue to hang around as long as they are in WAITING state. 1. Is it expected behavior that most tomcat threads are in RUNNABLE state? 2. If not, does it indicate a problem in the app or in tomcat configuration? My thinking

RE: Running out of tomcat threads - why many threads inRUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads inRUNNABLEstage even with no activity [Pantvaidya, Vishwajit] Thanks Rainer. The RUNNABLE thread - is it a connection between Tomcat and webserver, or between

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

On 20.05.2009 19:47, Caldarale, Charles R wrote: From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Subject: RE: Running out of tomcat threads - why many threads inRUNNABLEstage even with no activity - Setting connectionTimeout in server.xml seems to have resolved the issue Only

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

[Pantvaidya, Vishwajit] My problem is that tomcat is running out of threads (maxthreadcount=200). My analysis of the issue is: - threads count is exceeded because of a slow buildup of RUNNABLE threads (and not because number of simultaneous http requests at some point exceeded max thread

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Wednesday, May 20, 2009 11:53 AM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity On 20.05.2009 19:47, Caldarale, Charles R wrote

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

On 20.05.2009 00:53, Pantvaidya, Vishwajit wrote: -Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Monday, May 18, 2009 11:10 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Finally, is it possible that some bad code in the app could be hanging onto those RUNNABLE connections which is why tomcat

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

Finally, is it possible that some bad code in the app could be hanging onto those RUNNABLE connections which is why tomcat is not releasing them? Once more: NO, NO, NO! The threads you see in a RUNNABLE state are perfectly normal and expected. Go do the netstat that Rainer suggested

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Wednesday, May 20, 2009 11:53 AM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity On 20.05.2009 19:47, Caldarale, Charles R wrote

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Pantvaidya, Vishwajit wrote: - why do the 11 threads in the httpd o/p show port 21069 in foreign addr. Or are those not the correct threads I should be looking at?a A bit off-topic maybe, but if you add -p to netstat (at least under Linux), it will also show the program that corresponds to

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity if you add -p to netstat (at least under Linux), it will also show the program that corresponds to that line. Or at least -o to show the pid

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity On httpd machine Proto Recv-Q Send-Q Local Address Foreign Address State tcp1 0

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

The fact that *none* of the ports match would suggest (but not prove) that someone in the middle is closing the connections, and not telling either end about it. Do the netstat -anop again; it should be more interesting. - Chuck [Pantvaidya, Vishwajit] Tomcat server port 11065,

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

The fact that *none* of the ports match would suggest (but not prove) that someone in the middle is closing the connections, and not telling either end about it. Do the netstat -anop again; it should be more interesting. - Chuck [Pantvaidya, Vishwajit] Tomcat server port

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: vpant...@selectica.com To: users@tomcat.apache.org Date: Wed, 20 May 2009 15:17:15 -0700 Subject: RE: Running out of tomcat threads - why many threads

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: Martin Gainty [mailto:mgai...@hotmail.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp?topic=/ com.ibm.support.was40.doc/html/Plug_in/swg21163659.html Vaguely

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

This FAQ entry looks promising: http://tomcat.apache.org/connectors-doc/miscellaneous/faq.html Look at the entry entitled I've got a firewall between my web server and Tomcat which drops ajp13 connections after some time. Configuring keep-alives is a fairly low-overhead workaround, but it

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity So socket_keepalive is already 1. So does this mean that firewall is dropping connections in spite of it. The doc does

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

On 19.05.2009 02:54, Caldarale, Charles R wrote: From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Ok - so then the question is when does tomcat transition the thread from

Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 5/18/2009 8:54 PM, Caldarale, Charles R wrote: From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Ok - so

RE: Running out of tomcat threads - why many threads in RUNNABLEstageeven with no activity

From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstageeven with no activity Or, maybe Java's thread states don't differentiate between actually runnable and runnable but blocked (as opposed to WAITING

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Yes, sure - we will upgrade at some point of time. But since upgrading all our servers will be some work, that may not happen right away. Upgrading mod_jk is the least painful of all of these, and the most likely to affect you. [Pantvaidya, Vishwajit] I understand and agree and will

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Monday, May 18, 2009 11:10 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity On 19.05.2009 02:54, Caldarale, Charles R wrote

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Hi Chris, Thanks for your reply. On 5/13/2009 5:28 PM, Pantvaidya, Vishwajit wrote: My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using AJP1.3. Old versions of everything. Consider upgrading? [Pantvaidya, Vishwajit] Yes, sure - we will upgrade at some point of

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

On 13.05.2009 23:28, Pantvaidya, Vishwajit wrote: My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using AJP1.3. Every 2-3 days with no major load, tomcat throws the error: SEVERE: All threads (200) are currently busy, waiting... I have been monitoring my tomcat TP-Processor

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

On 14.05.2009 20:29, Pantvaidya, Vishwajit wrote: I set connectionTimeout in server.xml to 60 and now the RUNNABLE threads go back to WAITING stage after that time. But our other servers which are running the same configuration, same webapp and do not have connectionTimeout set in

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vishwajit, On 5/18/2009 2:01 PM, Pantvaidya, Vishwajit wrote: Yes, sure - we will upgrade at some point of time. But since upgrading all our servers will be some work, that may not happen right away. Upgrading mod_jk is the least painful of all

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

[Pantvaidya, Vishwajit] Here are figures from 3 of the servers which have not yet run out of threads (so the thread count does not add up to 200). I have taken these late at night when no users are present, so I was expecting all threads to be Waiting for tomcat thread-pool. 1. Total

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity [Pantvaidya, Vishwajit] Posting the thread dumps for the above 3 cases, The list usually filters out attachments, as it has done

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

[Pantvaidya, Vishwajit] Here are figures from 3 of the servers which have not yet run out of threads (so the thread count does not add up to 200). I have taken these late at night when no users are present, so I was expecting all threads to be Waiting for tomcat thread-pool.

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

Yes, those two look like waiting for next request on an existing connection from the web server to Tomcat and sitting idle in the pool, waiting for a new connection to handle. On 18.05.2009 22:44, Pantvaidya, Vishwajit wrote: [Pantvaidya, Vishwajit] Here are figures from 3 of the servers which

RE: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Monday, May 18, 2009 2:43 PM To: Tomcat Users List Subject: Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity Yes, those two look like waiting for next request

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity From whatever I have read on this, it seems to me that this could happen if a servlet writes something to a response stream

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

-Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Monday, May 18, 2009 4:02 PM To: Tomcat Users List Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity From: Pantvaidya, Vishwajit

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Ok - so then the question is when does tomcat transition the thread from Running to Waiting? Does that happen after AJP drops

RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity

From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] Subject: RE: Running out of tomcat threads - why many threads in RUNNABLEstage even with no activity Since I did not get any responses to this, just wanted to ask - did I post this to the wrong list and should I be posting

Re: Running out of tomcat threads - why many threads in RUNNABLE stage even with no activity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vishwajit, On 5/13/2009 5:28 PM, Pantvaidya, Vishwajit wrote: My setup is tomcat 5.5.17 + mod_jk 1.2.15 + httpd 2.2.2. I am using AJP1.3. Old versions of everything. Consider upgrading? Every 2-3 days with no major load, tomcat throws the

  1   2   >