log4j2

问题 I am struggling to write a simple POC program that logs messages to a Queue. All tutorials and Q&As I find (here and here) use log4j version 1.2 and they put messages onto a Topic and not onto a queue. My requirement is to log to a queue. I followed the documentation mentioned on the official site, but was not able to get it working. I have log4j2 and ActiveMQ JARs on my classpath, I have created the queue "logQueue", I am able to see the queue in the ActiveMQ web console and when I try

问题 I am trying to add new custom log4j2 appender. Karaf 3.0.2 use pax-logging 1.7.4 which does not support log4j2. I have a appender which extend org.apache.logging.log4j.core.appender.AbstractAppender . I followed this blog http://blog.nanthrax.net/2012/12/create-custom-log4j-appender-for-karaf-and-pax-logging/ writen by Jean-Baptiste. It will not work because my appender is written in log4j2. What are the alternatives so that karaf also log using this appender? 回答1: The answer is already in

问题 I have a java application in which I implemented logging. Here are the files log4j2.xml <configuration xmlns:xi="http://www.w3.org/2001/XInclude" status="WARN"> <xi:include href="log4j-xinclude-appenders.xml" /> <xi:include href="log4j-xinclude-loggers.xml" /> </configuration> log4j-xinclude-appenders.xml <appenders> <Console name="Console" target="SYSTEM_OUT"> <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/> </Console> <Routing name="RoutingAppender"> <Routes

问题 I have seen a log once that looked like this. Not sure what logging framework generated it. 12:34:56 INFO blah ... previous line repeated 23 times 11:22:33 DEBUG blah Can this be done with log4j2? 回答1: The current version, Log4j 2.6.2, does not have this capability. I'm not sure how easy it would be to implement this, but I would definitely recommend that you raise a feature request for this on the Log4j 2 issue tracker. A similar request may already exist to suppress repeated stack traces,

问题 I'm attempting to implement and configure a custom Filter in Log4J2 - based on ThresholdFilter, but intended to do more. I've seen topics on custom appenders, which follow the same plugin annotation syntax, but haven't found a topic on custom fitlers. MyCustomFilter.java (based on ThresholdFilter) @Plugin(name = "MyCustomFilter", category = Node.CATEGORY, elementType = Filter.ELEMENT_TYPE, printObject = true) public class MyCustomFilter extends AbstractFilter { private static final long

问题 I'm trying to set up a log4j2 SecureTcpSocketServer that will receive logs from a remote application (logging with log4j2). I've already prototyped this using the TcpSocketServer, which can be run from the command line by providing a port number and configuration file. The SecureTcpSocketServer however requires additional information to construct, such as a 'LogEventBridge' object and a 'SslConfiguration' object. I don't see how I could provide these objects to the command line so I decided

问题 I am trying to configure log4j for logging to database using JDBCAppender by referring to the below link. http://logging.apache.org/log4j/2.x/manual/appenders.html#JDBCAppender However I am getting the error "type GenericObjectPool does not take parameters". could some one please help me rectify this error? log4j2.xml <?xml version="1.0" encoding="UTF-8"?> <Configuration status="error"> <Appenders> <JDBC name="databaseAppender" tableName="LOGGING.APPLICATION_LOG"> <ConnectionFactory class=

问题 Log4j2 does not recreate log files if they were deleted in runtime. For example, careless admin have removed log-files where app currently write own logs. Actual result : logs doesn't write to file. Wanted result : log4j2 recreate file after first attempt to write into it and continue to work with this file. Manual recreating by cron or somehow else is not working because log4j2 "remembers" file descriptor of file and continiue to work with it even after old file was deleted and new was

问题 We have Spring java-based web deployments which use log4j2.xml for logging messages to files, etc. We now need to update our log4j2.xml configs in order to be able to do a ${web:contextPath} web lookup inside them so that we can use a deployment's context name as part of the log file's name which the loggers log messages to. However, when we deploy the apps, the log4j2 configurations fail to recognise any web lookup related stuff. The file created to log messages to is simply created with the

问题 I have a problem applying the log4j2.xml auto configuration properly, and I think it has something to do with my folder arrangement. I'm using maven to add log4j2 libs and arrange my projects as follows: - one project to contain all "common" classes, used by server and client side of my system. - another "core" project - the server side application. Both projects use the same general package hierarchy (like com.foo.specific.package ) In the Common project I define a logger wrapper: public