manage executor services centrally, to be re-used across applications
This is really needed now with the application per test (even more so if we go on to use one application per test case) because I frequently get OOME (unable to create native thread) when running the full test suite; this has been somewhat mitigated by using shutdownNow() on the executor when done. But still, executors should be discovered from configuration by name and reused. across the whole test suite. The rule is quite simple: self-created services are managed by the dispatcher, externally discovered ones are not. Then we also need a way to automatically time-out the thread-pool and shutdown as soon as the last dispatcher disconnects (plus 5 seconds or so).
Should timers be handled similarly but separately?
Should timers be handled similarly but separately?
Leave a comment
Central repository should be accessed with very simple get-or-create interface and return a very simple interface for dispatching tasks. This way the underlying implementation can be kept very simple ATM (just wrapping ExecutorService) but replaced with whatever the EPFL research comes up with later.
on 2011-11-22 15:43 *
By viktorklang
Assigned to changed from rkuhn to -none-
Milestone changed from 2.0-M1 to 2.0
Superceded by ExecutionContexts SIP