I only read the commit emails on my phone, so my understanding is still a bit superficial, but I noticed each @Scheduled element gets its own thread (up to max 5 threads, after that they start sharing). Why not use just one thread that executives all scheduled/submitted tasks?
Remko Sent from my iPhone > On 2015/11/17, at 12:25, Ralph Goers <[email protected]> wrote: > > I have checked in a CronTriggeringPolicy for the RollingFileAppenders on > branch LOG4J2-89. It also introduces the ConfigurationScheduler, a more > generic version of the ScheduledExecutorService I previously added. I am > envisioning that the scheduler can be used for more time-based tasks. Plugins > that use the Scheduler should be annotated with the Scheduled annotation to > help calculate the number of threads the scheduler should create. > > Please take a look at the branch and let me know what you think. > > Ralph > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
