Chris, I do have one other webapp deployed alongside, but neither of them ever gets reloaded. We always do a full stop/start of tomcat to roll out new builds (which is about the only time we ever stop these apps).
There's absolutely no performance penalty that I'm aware of. It was just the yet-unexplained recycling of threads. FWIW, we've got the pool based solution going now, so I'm off the whole ThreadLocal bandwagon (really really small wagon). This is uber low prio from my standpoint, in case you guys want to forget I ever brought it up. :-) Thanks, Dan On Wed, Sep 21, 2011 at 9:46 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dan, > > On 9/20/2011 4:47 PM, Dan Checkoway wrote: > > Thanks Chris. Those threads are *never* idle in this app. :-) > > They're still getting recycled periodically, it looks like, despite > > lack of idle time. > > Hmm, that does sound weird. Do you have other webapps also deployed > alongside this one? If you reload those webapps, the threads in the > thread pool will be recycled after a webapp undeployment to flush-out > any nasty stuff that might be tied to them. You can try setting the > "threadRenewalDelay" to a negative number to disable this particular > kind of recycling. > > > Does that make sense or am I on crack? > > You might still be on crack. > > Are you observing a performance penalty for this, or are you just > trying to explain an as-yet-unexplained recycling of threads? > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk556q0ACgkQ9CaO5/Lv0PADgwCfYqXFN9SBljy1LbEMUw2wEHpZ > 7NsAoK/kACgQm3tx+k9Uy0Xa9XyWIjEn > =g84G > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
