Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
1.1.0
-
None
Description
The ServerSocketReceiver and the AbstractServerSocketAppender and their subclasses are using the context's thread pool for client connections which is effectively limiting the amount of possible client connections to a little less than the value of the CoreConstants.MAX_POOL_SIZE which is 32.
In order to allow a flexible configuration of the client connections I recommend introducing a separate thread pool for the ServerSocketReceiver and the AbstractServerSocketAppender (one for each).
The user should be able to configure the core and max pool size to his needs.
Attachments
Issue Links
- relates to (out)
-
LOGBACK-1512 let SCHEDULED_EXECUTOR_POOL_SIZE be configurable
- Open