Re: CPU Utilization: log4j 2.6 and great

ed ones. And a study presented in April found that a compound in some sweet peppers (called CH-19 Sweet), which resembles capsaicin, provides similar positive metabolic effects > > > Original Message > From: DiFrango, Ronald > Sent: Saturday, Febr

Re: CPU Utilization: log4j 2.6 and great

CH-19 Sweet), which resembles capsaicin, provides similar positive metabolic effects Original Message From: DiFrango, Ronald Sent: Saturday, February 18, 2017 15:24 To: Log4J Users List Reply To: Log4J Users List Subject: Re: CPU Utilization: log4

Re: CPU Utilization: log4j 2.6 and great

18, 2017 15:24 To: Log4J Users List Reply To: Log4J Users List Subject: Re: CPU Utilization: log4j 2.6 and great Ralph, Sorry, we just figured it all out between Thursday and Friday, basically it came down to a combination of both version 2.6.2 and our own code ☹ Basically, if we upgrade to

Re: CPU Utilization: log4j 2.6 and great

Ralph, Sorry, we just figured it all out between Thursday and Friday, basically it came down to a combination of both version 2.6.2 and our own code ☹ Basically, if we upgrade to 2.7 and above, the utilization was still a little higher, but not nearly as bad as 2.6.2. Plus, like I said, we

Re: CPU Utilization: log4j 2.6 and great

Any news on this? Ralph > On Feb 13, 2017, at 5:00 PM, DiFrango, Ronald > wrote: > > We’re going to try and pull that for you as we’re still working through was > is going on. > > One question, though what would you use in place of the >

Re: CPU Utilization: log4j 2.6 and great

A value of max=2 means that the RolloverAppender ensures no more than 2 rolled over log files are kept. But all files in the directory are inspected. If the directory contains many files, the scan can take a while. An alternative is the action.

Re: CPU Utilization: log4j 2.6 and great

With a max of 2 I wouldn’t expect any problems. It does mean that you are only going to keep the last 2 files each day, and the last one might not be full as it might not be full when it rolls over at midnight. If maxFiles was 100 and you had more than 100 files per day then the time it would

Re: CPU Utilization: log4j 2.6 and great

I've seen cases where the "max" in caused issues because the directory contained many files that all needed to be scanned to see if they matched old log files to delete. That said, it would be good if you can share the results of jstack and do a run with Java Flight Recorder. Sent from my

Re: CPU Utilization: log4j 2.6 and great

If you are seeing lots of threads can you do a jstack on the process so we can see what they are? Ralph > On Feb 13, 2017, at 3:50 PM, DiFrango, Ronald > wrote: > > Our policy generally looks like the following where max log files is 2 and > size is 10MB and

Re: CPU Utilization: log4j 2.6 and great

The only threads in Log4j that I can think of that are short lived are the threads that compress the files at rollover. That would only consume a lot of CPU if rollover is happening a lot. Ralph > On Feb 13, 2017, at 1:12 PM, Christopher Schultz > wrote: > >

RE: CPU Utilization: log4j 2.6 and great

e: CPU Utilization: log4j 2.6 and great Ronald, On 2/13/17 2:29 PM, DiFrango, Ronald wrote: > Yeah, I’m aware and agreed, but this is done in the Apache HTTP Client > Component’s Code, not ours and existed as-is with log4j2 in ALL the versions > we’ve been using. > > That said, I think

Re: CPU Utilization: log4j 2.6 and great

Ronald, On 2/13/17 2:29 PM, DiFrango, Ronald wrote: > Yeah, I’m aware and agreed, but this is done in the Apache HTTP Client > Component’s Code, not ours and existed as-is with log4j2 in ALL the versions > we’ve been using. > > That said, I think this is a red herring and it’s still true that

Re: CPU Utilization: log4j 2.6 and great

Ralph, Yeah, I’m aware and agreed, but this is done in the Apache HTTP Client Component’s Code, not ours and existed as-is with log4j2 in ALL the versions we’ve been using. That said, I think this is a red herring and it’s still true that at least for our application any version of log4j2

Re: CPU Utilization: log4j 2.6 and great

The log.debug call will exit quickly, but if it is constructing a large message that will happen anyway unless one of the standard techniques (like wrapping in a logger.isDebugEnabled call) is used to avoid it. Constructing debug Strings can be expensive. Ralph > On Feb 13, 2017, at 10:58 AM,

Re: CPU Utilization: log4j 2.6 and great

No we are not and since it’s a log.debug() it should just get dropped on the floor before any sort of copying occurs, right? Ron DiFrango On 2/13/17, 12:50 PM, "Matt Sicker" wrote: Are you logging that info? On 13 February 2017 at 11:46, DiFrango, Ronald <

Re: CPU Utilization: log4j 2.6 and great

Are you logging that info? On 13 February 2017 at 11:46, DiFrango, Ronald < ronald.difra...@capitalone.com> wrote: > All, > > One thing we just noticed is that we are using Apache’s HTTP connection > pooling for our downstream calls and in our latest performance run is that > the READ operation

Re: CPU Utilization: log4j 2.6 and great

All, One thing we just noticed is that we are using Apache’s HTTP connection pooling for our downstream calls and in our latest performance run is that the READ operation on org.apache.http.impl.conn.LoggingInputStream seems to be taking a bulk of the time. If I look at the code, once the

Re: CPU Utilization: log4j 2.6 and great

This is running in Tomcat 8.0.33 in a Docker Container via AWS’s ECS which is identical to before with log4j2 2.5. We’ve run the application with Visual VM and the one thing for sure that we’ve seen is that in 2.6.2 it created tons of threads, something like 50+ but on 2.6 or 2.7 it was only

Re: CPU Utilization: log4j 2.6 and great

What server environment are you running this in? On 13 February 2017 at 09:19, Remko Popma wrote: > Ron, > > We haven't heard of any issues like you describe. > Have you tried running your application with Java Flight Recorder >

Re: CPU Utilization: log4j 2.6 and great

Ron, We haven't heard of any issues like you describe. Have you tried running your application with Java Flight Recorder ? This should help diagnose what is going on. Remko On Mon, Feb 13, 2017 at 9:59 PM,