[
https://issues.apache.org/jira/browse/LOG4J2-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geet S updated LOG4J2-3329:
---------------------------
Summary: OOM Issue: RollingFile with custom layout and timebased rolling
policy (was: RollingFile with custom layout and timebased rolling policy)
> OOM Issue: RollingFile with custom layout and timebased rolling policy
> ----------------------------------------------------------------------
>
> Key: LOG4J2-3329
> URL: https://issues.apache.org/jira/browse/LOG4J2-3329
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Layouts
> Affects Versions: 2.17.1
> Environment: CERTIFICATION
> Reporter: Geet S
> Priority: Blocker
>
> I have used Java log4j2 programmatically and created custom appender of type
> RollingFile with custom layout and TimeBasedTriggeringPolicy (interval 1800)
> . We see below issue for one component and this does not happen for all.
> We are using OpenJDK 1.8 with Embedded Jetty server 9.
>
>
>
> Error: java.lang.OutOfMemoryError: GC overhead limit exceeded
>
>
>
> Exception Trace:
>
> 2022-01-11 22:14:53,338 JobPublishingTask - 25 of 30 ERROR An exception
> occurred processing Appender CustomAppender
> org.apache.logging.log4j.core.appender.AppenderLoggingException:
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:165)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125)
> at
> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:542)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:500)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:483)
> at
> org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:417)
> at
> org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:82)
> at org.apache.logging.log4j.core.Logger.log(Logger.java:161)
> at
> org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2205)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2159)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2142)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1994)
> at
> org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1852)
> at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:1642)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
