|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
this also happens when specifying scan=true in the configuration file, i.e:
<configuration scan="true", scanPeriod="30 seconds" > ... </configuration>
in this scenario the threadpool is created via turbo filter ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter.
I think the best solution for this is to use a daemonized thread pool, will you guys accept a pull request implementing this? (a 5 liner, I guess)