On 18/05/2011 17:10, Dan Checkoway wrote: > Chris, > > Then I'd be faced with 400 (executor maxThreads) separate counter instances, > which doesn't solve the centralization thing I was looking for. Mark's > suggestion about using GlobalRequestProcessor seems to be doing the > trick...now if only it would be named consistently in mbean space... :-)
Why does it need to be consistent? A query should always find it regardless of the ordering. Mark > > Dan > > On Wed, May 18, 2011 at 12:06 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Dan, > > On 5/18/2011 8:21 AM, Dan Checkoway wrote: >>>> Gotcha...yeah, it would be trivial to slap an AtomicLong counter in a >>>> filter, but I'd hate to double the synchronization hit if tomcat already > has >>>> this counter available centrally. > > You could cheat and use a ThreadLocal :) > > -chris >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
