2016-12-08 69 views
0

我正在尝试使用JMSAppender log4j2向ActivMQ发送日志。使用JMSAppender发送2000条消息log4j2

我做了以下的conf

<?xml version="1.0" encoding="UTF-8"?> 
<Configuration monitorInterval="5"> 
    <Appenders> 
     <Console name="STDOUT" target="SYSTEM_OUT"> 
      <PatternLayout 
       pattern="%d{HH:mm:ss.SSS} %highlight{[%-5p] %c{1.} - %m} %style{(%t)}{Cyan}%n" /> 
     </Console> 
     <RollingFile name="fish" fileName="E:/fish/log/fish.server/fish.log" 
      filePattern="/log/fish.server/fish-%-d{yyyy-MM-dd-HH}.log"> 
      <PatternLayout pattern="%-d{yyyy-MM-dd HH:mm:ss.SSS} %5p %c{1} - %m%n" /> 
      <Policies> 
       <TimeBasedTriggeringPolicy /> 
      </Policies> 
     </RollingFile> 

     <JMS name="jmsQueue" destinationBindingName="logQueue" 
      factoryName="org.apache.activemq.jndi.ActiveMQInitialContextFactory" 
      factoryBindingName="ConnectionFactory" providerURL="tcp://xxxxxx:61616"> 
      <PatternLayout pattern="%-d{yyyy-MM-dd HH:mm:ss.SSS} %5p %c{1} - %m%n" /> 
     </JMS> 

    </Appenders> 
    <Loggers> 

     <Logger name="jmsLogger" level="warn"> 
      <AppenderRef ref="jmsQueue" /> 
     </Logger> 

     <Root level="warn"> 
      <!-- <AppenderRef ref="STDOUT" /> --> 
      <AppenderRef ref="fish" /> 
     </Root> 
    </Loggers> 
</Configuration> 

在那之后,我有32个线程streamExecutor其中做了一些工作人员,然后使用jmsLogger.warn(XXXX)的。

我曾经做过一个线程转储我的应用程序,我注意到以下阻断工作人员:?

"Log4j2-AsyncLogger[[email protected]]1" - Thread [email protected] 
    java.lang.Thread.State: WAITING 
    at sun.misc.Unsafe.park(Native Method) 
    - parking to wait for <324492ea> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) 
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) 
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) 
    at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) 
    at org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:40) 
    at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:87) 
    at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1366) 
    at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1305) 
    at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1795) 
    - locked <1af6596a> (a java.lang.Object) 
    at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:277) 
    at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:212) 
    at org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241) 
    at org.apache.logging.log4j.core.appender.mom.JmsAppender.append(JmsAppender.java:65) 
    at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:155) 
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:128) 
    at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:119) 
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) 
    at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:390) 
    at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:375) 
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:359) 
    at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:79) 
    at org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:310) 
    at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:149) 
    at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:45) 
    at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29) 
    at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
    at java.lang.Thread.run(Thread.java:745) 

所以现在的问题是,为什么在发送模式时线org.apache.activemq.ActiveMQConnection.syncSendPacket 。这造成了一些阻塞问题,并降低了我的表现。

Thnks很多:)

回答

1

由于Log4j的2.7的,我不知道有任何性能基准测试使用JMS的appender记录。大部分已发布的基准测试都是针对文件日志。即使在多线程应用程序中,Log4j2也可以同步记录800K msg/sec到一个文件,持续,。异步日志可以快多倍地处理突发事件。

相比之下,2000 msg/sec似乎不是一个非常高的数字。我猜这取决于JMS实现库的吞吐量。

+0

是的,我试图使用log4j 2.6实现JMSAppender。性能看起来非常好,因为lo4j 2.6使用最新的分销商库。我可以在0.125ms内发送25K msg。所以这是对我的问题的回应。我刚刚错过了一些配置。此实现的目标是避免写入文件并将此部分委托给其他进程(logstash elasticsearch kibana)的成本。 Thnks为答案 – user3021914