Jon Stevens <[EMAIL PROTECTED]> writes:
> on 12/2/2000 5:48 AM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
>
> > GlobalCacheService (for items expiry/refresh)
> > TurbineSchedulerService has its own thread, and also spawns
> > WorkerThreads
> > (the WorkerThreads should not be treated as daemon threads)
> > IDBroker uses a thread
> > LargeSelect class performs some operation in a separate thread, but it
> > should be treated as user thread rather than daemon.
> >
> > I'm +1 to making the threads of GlobalCache, Scheduler and IDBroker
> > daemon threads.
> > If there are no voices agains that I'll comit the changes in a few days.
> >
> > Rafal
> >
> > PS. Thanks for the idea Santiago!
>
> +1 as well. I also believe the database code spawns a thread as well...might
> not though...just check to be sure.
The PoolBrokerService does indeed now spawn a Monitor thread to watch
the DBConnections of each ConnectionPool.
Daniel
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
