On Fri, Mar 7, 2014 at 11:21 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > > Neven, > > On 3/5/14, 8:25 PM, Neven Cvetkovic wrote: > > On Wed, Mar 5, 2014 at 3:15 PM, S Ahmed <sahmed1...@gmail.com> > >> > > Ahmed, thanks for asking this question - it is sometimes very > > confusing with all different kind of pools: connection pools, > > threadpools, etc... > > > > Chris pointed out already - the connection pool does not have any > > threads... It is not a process that runs in the background, these > > are just connection objects that are sitting in memory. > > The connection pool does not "run in the background". The code > executes when a request-processing thread requests a connection. > Threads execute code. Code doesn't execute or "run" itself. > > +1
Chris, thanks for the clarification. That's what I meant (/said) - the connection pool is NOT a process, but code (object in memory) that gets executed by the request-processing thread. :)
