![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0.1 |
|
Assignee:
|
Logback dev list
|
|
Components:
|
logback-core |
|
Created:
|
08/Jan/13 2:23 PM
|
|
Description:
|
In ch.qos.logback.core.rolling.helper.AsynchronousCompressor.compressAsynchronously(String, String, String), a new thread pool is allocated every time to run a single Runnable. When I restart the application, sometimes logback invokes this code hundreds or thousands of times with temporary log file names that do not even exist. For each such invocation, a new thread pool is created, making Eclipse's debugger view with the thread list jump/flash as the new thread is created/removed. Even not considering that, this is a very bad usage of resources. Why not have a fixed thread pool and use it for all asynchronous executions?
|
|
Environment:
|
Windows 7/Java7
|
|
Project:
|
logback
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
KOVACS Istvan
|
|
|
|
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
|
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
