Title: Message Title
|
|
I can see two possibilities here:
-
Go back to having separate thread pools for executing different types of task. (Logback 1.1.6 had an AsynchronousCompressor class that executed each compression task in its own 1-thread pool. This meant the tasks did always run as soon as they were submitted.) Or at least ensure the long-running connection-accepting and connection-handling tasks are run separately from the 'quick' tasks like log file compression.
-
Increase the size of the per-context executor thread pool. It's hardcoded to 2 threads (ExecutorServiceUtil & CoreConstants) Or make the thread pool size configurable.
|
|
|
|
|
|
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev