[
https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332171#comment-15332171
]
Ralph Goers commented on LOG4J2-1430:
-------------------------------------
I would prefer an implementation where no configuration is required. If the
Disruptor is available then it should be used instead of the
ArrayBlockingQueue. You can do that by having two BlockingQueueFactory
implementations and just use the interface in the AsyncAppender. Then choose
the Disruptor implementation of the factory if a particular class in it is
available.
> Add support for custom BlockingQueue implementations in AsyncAppender
> ---------------------------------------------------------------------
>
> Key: LOG4J2-1430
> URL: https://issues.apache.org/jira/browse/LOG4J2-1430
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 2.6.1
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> For example, [this disruptor
> implementation|https://github.com/conversant/disruptor] works as an
> implementation of BlockingQueue that is much faster than ArrayBlockingQueue.
> If a sort of BlockingQueueFactory can be specified via a log4j system
> property, then it could be used by AsyncAppenders.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
