You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Michal Singer <Mi...@expand.com> on 2009/12/15 10:24:52 UTC
Accumulation of Request Processors objects causes tomcat stuck?
Hi, i am running an application on tomcat which gets stuck when processing
incoming messages after a while. I see accumulation of request processors
objects
in jconsole under: Catalina\RequestProcessor\http-8080.
What do these objects mean, what does it mean that they accumulate? can it
explain tomcat's getting stuck?
Thanks
--
View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26791905.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: motit [mailto:Moti.Tal@expand.com]
> Subject: RE: Accumulation of Request Processors objects causes tomcat
> stuck?
>
> As for my understanding the NIO conector has a single worker thread.
Not true. The NIO connector has one thread that monitors connection states, but when a request arrives, it is passed off to a worker thread from the pool. The big advantage of NIO is that no threads are dedicated to a connection, so persistent connections and keep-alives do not consume resources, at the cost of some switching overhead.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by motit <Mo...@expand.com>.
When using the same executer for two connectors which one is standard and the
other is NIO, can we benefit from the the NIO connector at all? As for my
understanding the NIO conector has a single worker thread.
Thanks in advance
Moti
Caldarale, Charles R wrote:
>
>> From: Michal Singer [mailto:Michal.Singer@expand.com]
>> Subject: RE: Accumulation of Request Processors objects causes tomcat
>> stuck?
>>
>> Uploaded server.xml
>
> Your <Executor> elements have no attributes other than names, so you're
> using the defaults. To quote from the doc:
> "minSpareThreads (int) The minimum number of threads always kept alive,
> default is 25"
>
> Since you have three <Executor>s, you'll see at least 75 threads hanging
> around all the time (once they've been created). The RequestProcessor
> items you see in the MBeans tab are just information about the last
> request each thread handled.
>
> Again, if you think Tomcat is stalled, take several thread dumps; browsing
> the MBeans isn't going to help.
>
>> <Engine className="com.expand.expandview.tomcat.ExpandViewStandardEngine"
>> defaultHost="localhost" name="Catalina">
>
> Using your own Engine class? Gutsy...
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26825788.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by Michal Singer <Mi...@expand.com>.
The engine class only does some initialization, we did not implement it all
:-)
Thanks
Caldarale, Charles R wrote:
>
>> From: Michal Singer [mailto:Michal.Singer@expand.com]
>> Subject: RE: Accumulation of Request Processors objects causes tomcat
>> stuck?
>>
>> Uploaded server.xml
>
> Your <Executor> elements have no attributes other than names, so you're
> using the defaults. To quote from the doc:
> "minSpareThreads (int) The minimum number of threads always kept alive,
> default is 25"
>
> Since you have three <Executor>s, you'll see at least 75 threads hanging
> around all the time (once they've been created). The RequestProcessor
> items you see in the MBeans tab are just information about the last
> request each thread handled.
>
> Again, if you think Tomcat is stalled, take several thread dumps; browsing
> the MBeans isn't going to help.
>
>> <Engine className="com.expand.expandview.tomcat.ExpandViewStandardEngine"
>> defaultHost="localhost" name="Catalina">
>
> Using your own Engine class? Gutsy...
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26823241.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Michal Singer [mailto:Michal.Singer@expand.com]
> Subject: RE: Accumulation of Request Processors objects causes tomcat
> stuck?
>
> Uploaded server.xml
Your <Executor> elements have no attributes other than names, so you're using the defaults. To quote from the doc:
"minSpareThreads (int) The minimum number of threads always kept alive, default is 25"
Since you have three <Executor>s, you'll see at least 75 threads hanging around all the time (once they've been created). The RequestProcessor items you see in the MBeans tab are just information about the last request each thread handled.
Again, if you think Tomcat is stalled, take several thread dumps; browsing the MBeans isn't going to help.
> <Engine className="com.expand.expandview.tomcat.ExpandViewStandardEngine"
> defaultHost="localhost" name="Catalina">
Using your own Engine class? Gutsy...
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by Michal Singer <Mi...@expand.com>.
Uploaded server.xml
Caldarale, Charles R wrote:
>
>> From: Michal Singer [mailto:Michal.Singer@expand.com]
>> Subject: Re: Accumulation of Request Processors objects causes tomcat
>> stuck?
>>
>> i am using <Executor> in the configuration of the connectors
>
> Might want to post your server.xml so we can take a look at it.
>
>> if i understand you correctly, it means that the requestors
>> are supposed to reduce?
>
> If they're not all busy, idle ones will terminate after some time period,
> down to the configured (or default) minimum for the <Executor>.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
http://old.nabble.com/file/p26806888/server.xml server.xml
--
View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26806888.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Michal Singer [mailto:Michal.Singer@expand.com]
> Subject: Re: Accumulation of Request Processors objects causes tomcat
> stuck?
>
> i am using <Executor> in the configuration of the connectors
Might want to post your server.xml so we can take a look at it.
> if i understand you correctly, it means that the requestors
> are supposed to reduce?
If they're not all busy, idle ones will terminate after some time period, down to the configured (or default) minimum for the <Executor>.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Accumulation of Request Processors objects causes tomcat
> stuck?
>
> That depends on your configuration. Why not post the <Connector> and
> <Executor> elements and we can take a look?
He already did:
http://marc.info/?l=tomcat-user&m=126094588620952&w=2
(Look at the end of the message.)
And I already commented on it:
http://marc.info/?l=tomcat-user&m=126097523027043&w=2
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Accumulation of Request Processors objects causes tomcat stuck?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michal,
On 12/16/2009 1:23 AM, Michal Singer wrote:
> I am using <Executor> in the configuration of the
> connectors, and so if i understand you correctly, it means that the
> requestors are supposed to reduce?
That depends on your configuration. Why not post the <Connector> and
<Executor> elements and we can take a look?
> at least after i see that messages are stuck.
> Second, i am using apache-tomcat-6.0.18, jdk1.6.0_12, running on Windows XP.
Thanks for the into.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksqlS0ACgkQ9CaO5/Lv0PAW/ACgrAkUlJ6AEUs3PYELUNgxJ1l6
ZPUAn07AQLcenAOaoe/UoERWnzzH0gS1
=g8tx
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Accumulation of Request Processors objects causes tomcat stuck?
Posted by Michal Singer <Mi...@expand.com>.
Hi. First of all, i am using <Executor> in the configuration of the
connectors, and so if i understand you correctly, it means that the
requestors are supposed to reduce? at least after i see that messages are
stuck.
Second, i am using apache-tomcat-6.0.18, jdk1.6.0_12, running on Windows XP.
While you're at it, tell us the Tomcat version, JVM version, and platform
you're running on.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Michal,
>
> On 12/15/2009 9:55 AM, Caldarale, Charles R wrote:
>>> From: Michal Singer [mailto:Michal.Singer@expand.com]
>>> Subject: Accumulation of Request Processors objects causes tomcat
>>> stuck?
>>>
>>> i am running an application on tomcat which gets stuck when
>>> processing incoming messages after a while.
>>
>> So take a thread dump and find out what they're waiting for.
>>
>> While you're at it, tell us the Tomcat version, JVM version, and platform
>> you're running on.
>>
>>> I see accumulation of request processors objects
>>> in jconsole under: Catalina\RequestProcessor\http-8080.
>>> What do these objects mean, what does it mean that they accumulate?
>>
>> That's normal; those are threads Tomcat creates to process requests.
>
> More specifically, unless you are using an <Executor> (unless you set
> this up yourself, you are not), your <Connector> will allocate as many
> threads as are required to serve the client demand (up to the configured
> maxThreads), but will never release them. <Executors> are smarter than
> that and can take request processor threads out of service if you feel
> strongly about reducing the number of idle threads.
>
> So, the presence of lots of threads is not a direct indication that
> anything is amiss.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAksnt/IACgkQ9CaO5/Lv0PDbFACeL2ah5EhTDSje6gN6fav3jL43
> etEAnjtzOPtQPba8a4BtEhfBaUtbVuSq
> =cUGp
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Accumulation-of-Request-Processors-objects-causes-tomcat-stuck--tp26791905p26806770.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Accumulation of Request Processors objects causes tomcat stuck?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michal,
On 12/15/2009 9:55 AM, Caldarale, Charles R wrote:
>> From: Michal Singer [mailto:Michal.Singer@expand.com]
>> Subject: Accumulation of Request Processors objects causes tomcat
>> stuck?
>>
>> i am running an application on tomcat which gets stuck when
>> processing incoming messages after a while.
>
> So take a thread dump and find out what they're waiting for.
>
> While you're at it, tell us the Tomcat version, JVM version, and platform you're running on.
>
>> I see accumulation of request processors objects
>> in jconsole under: Catalina\RequestProcessor\http-8080.
>> What do these objects mean, what does it mean that they accumulate?
>
> That's normal; those are threads Tomcat creates to process requests.
More specifically, unless you are using an <Executor> (unless you set
this up yourself, you are not), your <Connector> will allocate as many
threads as are required to serve the client demand (up to the configured
maxThreads), but will never release them. <Executors> are smarter than
that and can take request processor threads out of service if you feel
strongly about reducing the number of idle threads.
So, the presence of lots of threads is not a direct indication that
anything is amiss.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAksnt/IACgkQ9CaO5/Lv0PDbFACeL2ah5EhTDSje6gN6fav3jL43
etEAnjtzOPtQPba8a4BtEhfBaUtbVuSq
=cUGp
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Accumulation of Request Processors objects causes tomcat stuck?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Michal Singer [mailto:Michal.Singer@expand.com]
> Subject: Accumulation of Request Processors objects causes tomcat
> stuck?
>
> i am running an application on tomcat which gets stuck when
> processing incoming messages after a while.
So take a thread dump and find out what they're waiting for.
While you're at it, tell us the Tomcat version, JVM version, and platform you're running on.
> I see accumulation of request processors objects
> in jconsole under: Catalina\RequestProcessor\http-8080.
> What do these objects mean, what does it mean that they accumulate?
That's normal; those are threads Tomcat creates to process requests.
> can it explain tomcat's getting stuck?
No, but a thread dump will show what in your webapp or database they're stuck on.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org