当来自应用程序的大量日志记录时,Log4j2异步日志记录被卡住

时间:2020-01-17 07:29:15

标签: java log4j2 disruptor-pattern

我们的一个应用程序遇到了一个问题,即峰值负载导致log4j2挂起,而应用程序没有响应。 log4j2.xml

  1. 我们有一个CustomAppender,AppMessageAppender可以满足我们的应用程序需求。
  2. 当我们的应用程序出现突发事件时,我们看到的速度接近350行/秒。
  3. 它在短暂爆发后就关闭了,但是应用程序仍然没有响应。
  4. 我们尝试将的默认值从首先增加到现在的1024,然后再增加到2048。但我们仍然看到相同的问题。
  5. 我们将默认的log4j2.asyncLoggerConfigWaitStrategy设置为默认值(超时)。
  6. log4j2.xml如下所示。
AutoPilot
  1. 自定义记录器代码如下。
data: JSON.stringify({ arr: stringifiedArr })
  1. 应用程序AppMessageAppender侦听JMS队列并记录消息。
    <?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN" name="myApplication" packages="com.application.logging.log4j">
    <Properties>        
        <Property name="logLocation">./log</Property> <!-- current directory-->
        <Property name="filename">application</Property>
        <Property name="maxLogFileSize">50 MB</Property>
        <Property name="rolloverCount">20</Property>
    </Properties>
    <Loggers>
        <AsyncRoot level="WARN">
            <AppenderRef ref="STDOUT"/>
            <AppenderRef ref="STDERR" level="ERROR"/>
            <AppenderRef ref="File"/>
            <AppenderRef ref="FileErr" level="ERROR"/>
        </AsyncRoot>
        <AsyncLogger name="com.application" level="INFO" additivity="false">
            <AppenderRef ref="STDOUT"/>
            <AppenderRef ref="STDERR" level="ERROR"/>
            <AppenderRef ref="File"/>
            <AppenderRef ref="FileErr" level="ERROR"/>
        </AsyncLogger>
        <AsyncLogger name="CustomLogger" level="INFO" additivity="false">
            <AppenderRef ref="Message"/>
        </AsyncLogger>

        <AsyncLogger name="com.application" level="INFO" additivity="false">
            <AppenderRef ref="STDOUT"/>
            <AppenderRef ref="STDERR" level="ERROR"/>
            <AppenderRef ref="File"/>
            <AppenderRef ref="FileErr" level="ERROR"/>
        </AsyncLogger>      
    </Loggers>
    <Appenders>
        <Console name="STDOUT" target="SYSTEM_OUT">
            <PatternLayout pattern="[^%d^] [^%-5level^] [^%t^] - [^%msg^]%n"/>
        </Console>
        <Console name="STDERR" target="SYSTEM_ERR">
            <PatternLayout pattern="[^%d^] [^%-5level^] [^%t^] - [^%msg^]%n"/>
        </Console>
        <RollingRandomAccessFile name="File" fileName="${logLocation}/${filename}.log" filePattern="${logLocation}/${filename}-%d{MM-dd-yyyy}-%i.log" immediateFlush="false">
            <PatternLayout pattern="[^%d^] [^%-5level^] [^%t^] - [^%msg^]%n"/>
            <Policies>
                <TimeBasedTriggeringPolicy />
                <SizeBasedTriggeringPolicy size="${maxLogFileSize}"/>
            </Policies>
            <DefaultRolloverStrategy max="${rolloverCount}"/>
        </RollingRandomAccessFile>
        <RollingRandomAccessFile name="FileErr" fileName="${logLocation}/${filename}_err.log" filePattern="${logLocation}/${filename}_err-%d{MM-dd-yyyy}-%i.log" immediateFlush="false">
            <PatternLayout pattern="[^%d^] [^%-5level^] [^%t^] - [^%msg^]%n"/>
            <Policies>
                <TimeBasedTriggeringPolicy />
                <SizeBasedTriggeringPolicy size="${maxLogFileSize}"/>
            </Policies>
            <DefaultRolloverStrategy max="${rolloverCount}"/>
        </RollingRandomAccessFile>
        <RollingRandomAccessFile name="FileMetrics" fileName="${logLocation}/${filename}_metrics.log" filePattern="${logLocation}/${filename}_metrics-%d{MM-dd-yyyy}-%i.log" immediateFlush="false">
            <PatternLayout pattern="%msg%n"/>
            <Policies>
                <SizeBasedTriggeringPolicy size="${maxLogFileSize}"/>
            </Policies>
            <DefaultRolloverStrategy max="${rolloverCount}"/>
        </RollingRandomAccessFile>
        <AppMessageAppender name="Message" directory="${logLocation}/messages"/>
    </Appenders>
</Configuration>
  1. 我们也有一个CustomMessage类。
    package com.application.logging;

    import java.net.URL;

    import org.apache.logging.log4j.LogManager;
    import org.apache.logging.log4j.Logger;

    public final class Log4j2Logger {

        private static final String DEFAULT_CATEGORY = "com.application";

        private Logger log;

        static {
            configureLogger();
        }

        public Logger(String category){
            this.category = category;
        }

        /**
         * Constructs Log4jLogger with default ("com.application") category
         */
        public Log4j2Logger(){
            log = LogManager.getLogger(DEFAULT_CATEGORY);
        }

        /**
         * Constructs Log4jLogger with given category
         * @param category
         */
        public Log4j2Logger(String category){
            super(category);
            log = LogManager.getLogger(category);
        }   
        /**
         * Constructs Log4jLogger with given class
         * @param clazz
         */
        public Log4j2Logger(Class clazz){
            super(clazz);
            log = LogManager.getLogger(clazz.getName());
        }

        /**
         * Log message at debug level
         * @param message
         */
        public void debug(Object message){
            log.debug(message);
        }

        /**
         * Log exception with given message at debug level
         * @param message
         * @param t
         */
        public void debug(Object message, Throwable t){
            log.debug(message,t);
        }

        /**
         * Log message at info level
         * @param message
         */
        public void info(Object message){
            log.info(message);
        }

        /**
         * Log exception with given message at info level
         * @param message
         * @param t
         */
        public void info(Object message, Throwable t){
            log.info(message,t);
        }

        /**
         * Log message at warn level
         * @param message
         */
        public void warn(Object message){
            log.warn(message);
        }

        /**
         * Log exception with given message at warn level
         * @param message
         * @param t
         */
        public void warn(Object message, Throwable t){
            log.warn(message,t);
        }

        /**
         * Log message at error level
         * @param message
         */
        public void error(Object message){
            log.error(message);
        }

        /**
         * Log exception with given message at error level
         * @param message
         * @param t
         */
        public void error(Object message, Throwable t){
            log.error(message,t);
        }

        /**
         * Log message at fatal level
         * @param message
         */
        public void fatal(Object message){
            log.fatal(message);
        }

        /**
         * Log exception with given message at fatal level
         * @param message
         * @param t
         */
        public void fatal(Object message, Throwable t){
            log.fatal(message,t);
        }

        @Override
        public void debug(String message) {
            log.debug(message);
        }

        @Override
        public void debug(String message, Throwable t) {
            log.debug(message,t);
        }

        @Override
        public void error(String message) {
            log.error(message);
        }

        @Override
        public void error(String message, Throwable t) {
            log.error(message,t);
        }

        @Override
        public void fatal(String message) {
            log.fatal(message);     
        }

        @Override
        public void fatal(String message, Throwable t) {
            log.fatal(message,t);
        }

        @Override
        public void info(String message) {
            log.info(message);
        }

        @Override
        public void info(String message, Throwable t) {
            log.info(message,t);
        }

        @Override
        public void warn(String message) {
            log.warn(message);
        }

        @Override
        public void warn(String message, Throwable t) {
            log.warn(message,t);
        }   

        @Override
        public boolean isTraceEnabled() {
            return log.isTraceEnabled();
        }

        @Override
        public void trace(Object message) {
            log.trace(message);     
        }

        @Override
        public void trace(Object message, Throwable t) {
            log.trace(message,t);
        }

        @Override
        public void trace(String message) {
            log.trace(message);
        }

        @Override
        public void trace(String message, Throwable t) {
            log.trace(message,t);
        }

        /**
         * @return true if debug level log is enabled
         */
        public boolean isDebugEnabled(){
            return log.isDebugEnabled();
        }


        public boolean isInfoEnabled(){
            return log.isInfoEnabled();
        }

        public boolean isEnableForLevel(com.application.Level level){
            return log.isEnabled(((Log4j2Level)level).getLog4jLevel());
        }

        public com.application.loggging.Level getLogLevel(){
            return Log4j2Level.convert2Log4j(log.getLevel());

        }

        public void setLogLevel(com.application.Level level){
            ((org.apache.logging.log4j.core.Logger)log).setLevel(((Log4j2Level)level).getLog4jLevel());
        }

        private static void configureLogger(){
            System.setProperty("Log4jContextSelector","org.apache.logging.log4j.core.async.AsyncLoggerContextSelector");
            System.setProperty("AsyncLogger.ThreadNameStrategy","UNCACHED");
            mbean.setSystemProperties();
            try{
                URL url = Thread.currentThread().getContextClassLoader().getResource("log4j2.xml");
                if(url != null){
                    System.setProperty("log4j.configurationFile",url.toString());
                }else{
                    System.err.println("No log4j2.xml configuration found in the classpath logger");
                }
                Log4j2Logger logger = new Log4j2Logger();
                logger.info("Log4j2 logger configured");
            }catch(Exception e){
                e.printStackTrace();
            }
        }
    }
  1. 当我们查看问题期间的线程转储时,我们看到了很多带有打击堆栈跟踪的线程。
  package com.application.logging;

   import java.io.BufferedWriter;
   import java.io.File;
   import java.io.FileNotFoundException;
   import java.io.FileWriter;
   import java.io.IOException;
   import java.io.Serializable;
   import java.io.Writer;
   import java.util.Date;`
   import java.util.Properties;
   import java.util.concurrent.atomic.AtomicLong;

   import org.apache.commons.lang.time.FastDateFormat;
   import org.apache.log4j.helpers.LogLog;
   import org.apache.logging.log4j.core.Filter;
   import org.apache.logging.log4j.core.Layout;
   import org.apache.logging.log4j.core.LogEvent;
   import org.apache.logging.log4j.core.appender.AbstractAppender;
   import org.apache.logging.log4j.core.config.Configuration;
   import org.apache.logging.log4j.core.config.plugins.Plugin;
   import org.apache.logging.log4j.core.config.plugins.PluginAttribute;
   import org.apache.logging.log4j.core.config.plugins.PluginConfiguration;
   import org.apache.logging.log4j.core.config.plugins.PluginElement;
   import org.apache.logging.log4j.core.config.plugins.PluginFactory;
   import org.apache.logging.log4j.core.layout.PatternLayout;
   import org.slf4j.Logger;
   import org.slf4j.LoggerFactory;

   import com.application.logging.CustomMessage;
   import com.application.framework.utils.PropertiesCache;
   import com.application.utils.xml.SpringBeanFactory;

   @Plugin(name = "AppMessageAppender", category = "Core", elementType = "appender", printObject = true)
   public final class AppMessageAppender extends AbstractAppender {

       private static final long serialVersionUID = 1L;
       private static final String DEFAULT_DATE_FORMAT = "dd_MM_yyyy/HH";
       private static final String DEFAULT_TIME_FORMAT = "HHmmss_SSS";

       private static Logger logger = LoggerFactory.getLogger(AppMessageAppender.class);
       private String directoryName;
       private String dirTimeFormat = DEFAULT_DATE_FORMAT;
       private FastDateFormat dateFormatter;
       private static FastDateFormat timeFormatter = FastDateFormat.getInstance(DEFAULT_TIME_FORMAT);
       private AtomicLong sequenceNo = new AtomicLong();

       protected AppMessageAppender(String name, Filter filter, Layout<? extends Serializable> layout,
               String directoryName, String subDirectoryDateFormat) {
           super(name, filter, layout);
           this.directoryName = directoryName;
           if (subDirectoryDateFormat != null)
               this.dirTimeFormat = subDirectoryDateFormat;
           dateFormatter = FastDateFormat.getInstance(dirTimeFormat);
       }

       @Override
       public void append(LogEvent event) {
           Writer writer = null;
           try {
               CustomMessage logMessage = (CustomMessage) event.getMessage().getParameters()[0];
               StringBuilder sb = new StringBuilder();
               if (directoryName != null) {
                   sb.append(directoryName).append("/");
               }
               Date d = new Date(event.getTimeMillis());
               sb.append(dateFormatter.format(d)).append("/").append(logMessage.getChannel());
               String dir = sb.toString();
               String processMessageId = logMessage.getMessageId();
               sb.append("/Msg_").append(logMessage.getMessageId().replaceAll("/", "")).append("_")
                       .append(timeFormatter.format(d)).append("_").append(sequenceNo.getAndIncrement())
                       .append(".log");
               String absFile = sb.toString();
               writer = writeToFile(logMessage, dir, absFile);
               logger.info("AppMessageAppender message logged: {} ", absFile);
               String channelType = logMessage.getChannel();
               Properties auditPropConfig = PropertiesCache.getAuditChannelCapability();
               String beanName = auditPropConfig.getProperty(channelType);
           } catch (IOException e) {
               LogLog.error("Exception in writing to file", e);
           } finally {
               if (writer != null) {
                   try {
                       writer.close();
                   } catch (IOException e) {
                       logger.error("Error in closing the stream");
                   }
               }
           }
       }

       private Writer writeToFile(CustomMessage logMessage, String dir, String absFile) throws IOException {
           Writer writer;
           try {
               writer = new BufferedWriter(new FileWriter(absFile));
           } catch (FileNotFoundException fne) {
               File f = new File(dir);
               f.mkdirs();
               writer = new BufferedWriter(new FileWriter(absFile));
           }
           logMessage.write(writer);
           writer.flush();
           return writer;
       }

       @PluginFactory
       public static AppMessageAppender createAppender(@PluginAttribute("name") String name,
               @PluginElement("Filter")
               final Filter filter, @PluginElement("Layout") Layout<? extends Serializable> layout,
               @PluginAttribute("directory")
               final String directoryName, @PluginAttribute("subDirectoryDateFormat")
               final String subDirectoryDateFormat, @PluginConfiguration
               final Configuration config) {
           if (layout == null) {
               layout = PatternLayout.createDefaultLayout();
           }
           return new AppMessageAppender(name, filter, layout, directoryName, subDirectoryDateFormat);
       }

   }

问题:

  1. 这是log4j2上的负载和破坏者无法处理的问题吗?
  2. 除了增加ringBuffersize之外,还可以进行其他优化吗?
  3. 我们正在使用log4j2 2.11.0和disruptor 3.4.1版本,在OEL 3.8.13-98.el6uek.x86_64中运行它,这些组合是否存在任何已知问题?

很高兴澄清任何其他要求。

快速编辑-:我们已经看到了一段时间。最初,日志与服务器时间戳同步,即日志与服务器时间戳匹配。随着时间的流逝,日志记录开始变慢,我们看到早于3个小时(有时为8个小时)的日志记录在日志中。我希望能在某处敲钟。

谢谢

1 个答案:

答案 0 :(得分:1)

我怀疑您的应用程序生成日志事件的速度超出了Appender的处理速度。该配置显示了两个ConsoleAppender。登录到控制台的费用为extremely slow,实际上比登录文件要慢50倍。

异步记录器使用环形缓冲区。如果此缓冲区已满(因为Appender无法足够快地取出事件),则该应用程序将无法向队列添加新事件,因此有效地阻止了该应用程序取得进展。

我的建议是仅将WARN或ERROR事件记录到控制台,并将其他所有内容记录到文件。

另一个潜在的瓶颈是自定义Appender。请注意,它将为每个事件打开一个新的FileWriter 。这将很慢。最好一次打开该文件并保持附加。