Re: Chainsaw Zeroconf FileAppender Error

I used jmdns 3.4.2 with the latest log4j2 and a sample app that used the following appender configuration to log to a local file. Chainsaw was able to discover the advertisement and live tail the log file. It looks like the latest JmDNS has changed their API, so log4j2 works with jmdns 3.4.1,

Fwd: Chainsaw Zeroconf FileAppender Error

-- Forwarded message -- From: Mohit Garg Date: Tue, Apr 18, 2017 at 10:24 PM Subject: Chainsaw Zeroconf FileAppender Error To: log4j-user@logging.apache.org Hi, I am using Apache Chainsaw on an Ubuntu 14.04 machine. In my Java application I have the advertised

Re: Using Log4J2 2.8 (via the 1.2 API Bridge) for Tomcat8 Internal Logging - RollingFileAppender does not (cannot?) create new Log File

On Monday, April 10, 2017 5:20 PM, Remko Popma wrote: >If you enable internal Log4j2 logging with at >the top of your configuration, then you should see internal Log4j2 logging on >the console. >It should show details of what happens during a rollover.

Re: anomalies running log4j v 2.2 on Tomcat

I can partially answer that. The LoggerContext name has changed a few times. I actually thought it's the other way around and the older versions of Log4j2 use a web app name-based LoggerContext name. It turned out that some web containers generate web context names that are multiple lines and

Re: Max index limit in DefaultRolloverStrategy

FYI - the documentation for the web site is in the project at src/site/xdoc/manual. You can create a patch for that the same way you would patch any of the java source. Ralph > On Apr 18, 2017, at 10:20 AM, Chandra > wrote: > > Hi Gary, > > I’d love

Re: Max index limit in DefaultRolloverStrategy

Hi Gary, I’d love to, but this ticket is primarily to change the documentation and it’d have a minor amendments in the document on the website. I’m not exactly sure how to send a patch to this :-/ 1) https://logging.apache.org/log4j/2.x/manual/appenders.html#DefaultRolloverStrategy

anomalies running log4j v 2.2 on Tomcat

I would be grateful for any input the members of this list can provide about the following situation. We are running Tomcat 8.0.39, deploying on it a number of web applications using log4j2, the jars for which are packaged into the war files. These webapps are built in various environments.

Re: Max index limit in DefaultRolloverStrategy

Patches welcome ;-) Gary On Apr 18, 2017 1:18 AM, "Chandra" wrote: Hi guys, any update on this ticket? https://issues.apache.org/jira/browse/LOG4J2-1877 thanks, Chandra On 12 Apr 2017, 12:14 AM +0530, Chandra ,

Re: Buffering in Console Appender?

Hello Mikael, this fix was already merged into Surefire. It made a massive difference difference in our cases: as confirmed by both data from Java Flight Recorder and real-world

Re: Max index limit in DefaultRolloverStrategy

Hi guys, any update on this ticket? https://issues.apache.org/jira/browse/LOG4J2-1877 thanks, Chandra On 12 Apr 2017, 12:14 AM +0530, Chandra , wrote: > Yes, that’d be great.  7 seems to too low for frequently filled logs. > And also guys, please document

Re: Buffering in Console Appender?

If you add this, don't forget to do some performance tests to verify that it actually improves performance. On Fri, Apr 14, 2017 at 1:33 PM, Jaromir Hamala wrote: > Hello Matt, > > thanks for you reply. I realized this is something what should > probably be handled