On Tue, Dec 1, 2009 at 3:28 PM, Jim Davidson <[email protected]> wrote: > On Dec 1, 2009, at 4:45 PM, Jeff Rogers wrote: >> >> I also don't understand why there can be multiple interps per server+thread >> combo in the first place (PopInterp/PushInterp); I'd expect that only one >> conn can be in a thread at a time and that it always releases the interp >> when it leaves the thread. > > > > I think there was an edge case that led to a need for a cache of possible > interps instead of just holding one. In practice, it's always just one > unless someone writes some weird code to do a pop/push directly to have some > alternate interp for a special purpose.
One thing which causes multiple interps per thread is the "default" threadpool. If you have a default threadpool the threads are shared across servers. So, as each server uses a thread, an interp for that server is created. My advice is to always register a default threadpool for each server so that the process wide default threadpool is never used. I'm not sure if there is any security problem, but a shared threadpool makes each thread more expensive, and I doubt it saves resources. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[email protected]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
