> From: David kerber [mailto:dcker...@verizon.net]
> I also have quite a few blocks like this:
[...]
> [2009-05-08 10:43:23] [info] - locked <0x0510e6e0> (a
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
[...]
> I assume these are just threads waiting for something to do
> (waiting for a request)?
They look like spares in the pool, but my knowledge of Tomcat's internals is
limited.
> Until you said that, I didn't even notice that I had what appear to be
> "double" synchronizations, making the method synchronized, and also
> having synchronized{} blocks inside it. I assume I've been
> double-screwing myself all this time??
Yeah, I did raise an eyebrow when I saw it. It'll take a few CPU cycles per
request, but no more than that. Only one thread can get into the method, so
any internal syncs just add overhead. They're not further places for
contention to occur.
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
