You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "samuel ma (Jira)" <ji...@apache.org> on 2019/09/11 09:32:00 UTC

[jira] [Updated] (LOG4J2-2691) Support to limit the message length

     [ https://issues.apache.org/jira/browse/LOG4J2-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

samuel ma updated LOG4J2-2691:
------------------------------
    Description: We are using log4j2 2.11.1 + disruptor, and running into a OutOfMemory Error. The reason is App log some huge message, and the consumer is very slow then disruptor RingBuffer is full.  Is that possible to limit the message length (not 'maxLen' in PatternLayout, maxLen is just the message length for layout) before RingBuffer enqueue by some configuration?  (was: We are using log4j2 2.11.1 + disruptor, and running into a OutOfMemory Error. The reason is App log some hug message, and the consumer is very slow then disruptor RingBuffer is full.  Is that possible to limit the message length (not 'maxLen' in PatternLayout, maxLen is just the message length for layout) before RingBuffer enqueue by some configuration?)
        Summary: Support to limit the message length  (was: Limit the message length support)

> Support to limit the message length
> -----------------------------------
>
>                 Key: LOG4J2-2691
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2691
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: samuel ma
>            Priority: Major
>
> We are using log4j2 2.11.1 + disruptor, and running into a OutOfMemory Error. The reason is App log some huge message, and the consumer is very slow then disruptor RingBuffer is full.  Is that possible to limit the message length (not 'maxLen' in PatternLayout, maxLen is just the message length for layout) before RingBuffer enqueue by some configuration?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)