log4j

1 、修改 log4j.properties vi /opt/zookeeper-3.4.8/conf/log4j.properties # Define some default values that can be overridden by system properties zookeeper.root.logger=INFO,ROLLINGFILE zookeeper.console.threshold=INFO zookeeper.log.dir=. zookeeper.log.file=zookeeper.log zookeeper.log.threshold=DEBUG zookeeper.tracelog.dir=. zookeeper.tracelog.file=zookeeper_trace.log … … # # Add ROLLINGFILE to rootLogger to get log file output # Log DEBUG level and above messages to a log file # 按照日期每天输出logs log4j.appender.ROLLINGFILE=org.apache.log4j.DailyRollingFileAppender log4j.appender.ROLLINGFILE.Threshold=$

My problem concerns logging of library classes (classes that are used inside libraries), We are currently using log4cxx but the log4j library implements the same concepts. Say i have a process that have several entities, A,B and C. Each of them use many different classes and functions, clearly separated in the code. A,B and C use many library classes, functions, objects, resources and sometimes even globals (legacy code, nothing i can do about it...) - let us call them all foo Logging A,B and C turned out to be a performance issue , the log gets blasted when we set the log level to debug.

I am trying to use logback-beagle in eclipse/kepler (java). As I understand it is not currently supported as listed below(?). http://marketplace.eclipse.org/content/logback-beagle#.Uv1cGPldWK8 I still went ahead and installed the plugin and dont see it under windows-preferences. Is there an alternative to get similar functionality (of color coding and navigating from log output of slf4j/log4j in eclipse) Or can I make beagle plugin work for eclipse(?). I dont understand why eclipse want to have it in marketplace, but doesnt show up in preferences after installing I just came across the same

I am trying to setup a project with slf4j + log4j, but the damn thing just doesn't work... I keep getting exception: Failed to instantiate SLF4J LoggerFactory Reported exception: java.lang.NoClassDefFoundError: org/apache/log4j/Level at org.slf4j.LoggerFactory.bind(LoggerFactory.java:129) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:302) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:276) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:288) at TestLog.main(TestLog.java:9) Caused by:

转载： https://www.cnblogs.com/jxwch/p/6526271.html zookeeper服务器会产生三类日志：事务日志、快照日志和log4j日志。 　　在zookeeper默认配置文件zoo.cfg（可以修改文件名）中有一个配置项dataDir，该配置项用于配置zookeeper快照日志和事务日志的存储地址。在官方提供的默认参考配置文件zoo_sample.cfg中，只有dataDir配置项。其实在实际应用中，还可以为事务日志专门配置存储地址，配置项名称为dataLogDir，在zoo_sample.cfg中并未体现出来。在没有dataLogDir配置项的时候，zookeeper默认将事务日志文件和快照日志文件都存储在dataDir对应的目录下。建议将事务日志（dataLogDir）与快照日志（dataLog）单独配置，因为当zookeeper集群进行频繁的数据读写操作时，会产生大量的事务日志信息，将两类日志分开存储会提高系统性能，而且，可以允许将两类日志存在在不同的存储介质上，减少磁盘压力。log4j用于记录zookeeper集群服务器运行日志，该日志的配置地址在conf/目录下的log4j.properties文件中，该文件中有一个配置项为“zookeeper.log.dir=.”，表示log4j日志文件在与执行程序（zkServer.sh

1、环境准备 操作系统：win10 开发工具：IntelliJ IDEA 数据库：MySQL 底层工具：dubbo admin（没有也完全可以） + zookeeper 框架：springMVC+mybatis 工程：maven 2、工程搭建后的结构图 开始搭建前，先看一下搭建好后的结构 其中：tea-api模块：接口和实体类的信息，也是暴露给服务调用者的模块 tea-service模块下的2个子模块：basic-service和biz-server，是服务提供者，basic是提供数据库层的服务，biz提供其他的，比如redis 的调用等，示例中，只是写了一段输出 tea-web模块下的crm-web模块，是服务调用者，对外展示的通道（crm嘛，当然就能想到后台管理系统了） 3、搭建前的准备 3.1、安装zookeeper 3.1.1、下载zookeeper 直接官网下载： https://www.apache.org/dyn/closer.cgi/zookeeper/ 3.1.2：修改zk 的配置文件 下载并且解压后，进入zk 的conf目录，将zoo_sample.cfg文件复制并命名为zoo.cfg，修改其中的配置： 如图中标红的，一个是zk 的节点存放目录，clientPort是zk 的端口 3.1.3：启动zk服务 改完后，保存，进入bin目录，执行zkServer

How do we know which is the right Appender to use between RollingFileAppender and FileAppender? You may want to read the Apache Log4j 1.2.17 API : org.apache.log4j.FileAppender FileAppender appends log events to a file. org.apache.log4j.RollingFileAppender RollingFileAppender extends FileAppender to backup the log files when they reach a certain size . 来源： https://stackoverflow.com/questions/25061780/can-log4j-1-2-whats-the-difference-between-rollingfileappender-and-fileappender

Log4J对系统性能的影响 主要体现： 1、日志输出的目的地，输出到控制台的速度比输出到文件系统的速度要慢。 2、日志输出格式不一样对性能也会有影响，如简单输出布局(SimpleLayout)比格式化输出布局(PatternLayout)输出速度要快。可以根据需要尽量采用简单输出布局格式输出日志信息。 3、日志级别越低输出的日志内容就越多，对系统系能影响很大。 4、日志输出方式的不同，对系统系能也是有一定影响的，采用异步输出方式比同步输出方式性能要高。 5、每次接收到日志输出事件就打印一条日志内容比当日志内容达到一定大小时打印系能要低。 优化方式： 1、组装输出内容之前可对logger的输出级别先进行判断而不要完全依赖log4j控制，因为组装输出日志内容也是要损耗效率的。 //若log4j并未开启info级日志记录，直接返回 if(!monitorLogger.isInfoEnabled()){ return; } 来源： https://www.cnblogs.com/ngrzr/p/11906354.html

解决方法 将pom.xml配置文件中关于log4j的版本由原先的1.2.17版本改为1.2.16 < log4j.version > 1.2.16 </ log4j.version > < dependency > < groupId > log4j </ groupId > < artifactId > log4j </ artifactId > < version > 1.2.16 </ version > </ dependency > 来源： CSDN 作者： wzz87 链接： https://blog.csdn.net/wzz87/article/details/80180626