https://bz.apache.org/bugzilla/show_bug.cgi?id=63078
--- Comment #29 from Remy Maucherat <r...@apache.org> --- (In reply to Rainer Jung from comment #28) > > (In reply to Rainer Jung from comment #25) > > > Wouldn't it be better to limit the queue and log any exception resulting > > > from the queue being full? > > > > Sure, try it ;) > > (read the scheduled executor javadoc first though) > > Thanks for the free lesson Rémy, so once we use ScheduledThreadPoolExecutor > the queue is fixed and can not be limited. I am frustrated by this :( It is also not possible to set a max thread count (it is always the core count), and expiring idle threads is bad too (it will periodically respawn the core threads instead of reducing live thread count). On the plus side, it is actually more robust in the real world than what we had before, since a task monitor is very easy to implement (there is one for all periodic tasks). The EE specification has a (more complete) scheduled executor API. (but it's not really worth doing it) https://docs.oracle.com/javaee/7/api/javax/enterprise/concurrent/ManagedScheduledExecutorService.html -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
