Re: Apache chainsaw

I’m wondering if in part Chainsaw died because of the ELK stack? Ron DiFrango On 4/9/17, 3:56 AM, "Robert Lu" wrote: Hi, all. I think developer need a tool to view, search log. Chainsaw was a great tool, but need update. I want to contribute to

Re: EDT Transition?

;Matt Sicker" <boa...@gmail.com> wrote: I'm guessing this is related to a bug I found yesterday in the tests: https://issues.apache.org/jira/browse/LOG4J2-1849 On 13 March 2017 at 09:19, DiFrango, Ronald <ronald.difra...@capitalone.com> wrote: &g

EDT Transition?

All, We’re in the EST/EDT timezone and we saw some odd behavior with our layout pattern where we had %d{DATE}. Basically, the times were reporting as EST until midnight then they properly started showing up as EDT. The interesting thing is that when we fixed it to be %d{dd MMM

Re: CPU Utilization: log4j 2.6 and great

. Ralph > On Feb 18, 2017, at 2:09 PM, DiFrango, Ronald <ronald.difra...@capitalone.com> wrote: > > Laurent, > > We had several problems: > > 1) We had two different roll-over strategies, > a. One being time based wit

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

<ralph.go...@dslextreme.com> wrote: Any news on this? Ralph > On Feb 13, 2017, at 5:00 PM, DiFrango, Ronald <ronald.difra...@capitalone.com> wrote: > > We’re going to try and pull that for you as we’re still working through was is going on. >

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

, 2017, at 10:58 AM, DiFrango, Ronald <ronald.difra...@capitalone.com> wrote: > > 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

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" <boa...@gmail.com> wrote: Are you logging that info? On 13 February 2017 at 11:46,

Re: CPU Utilization: log4j 2.6 and great

DiFrango On 2/13/17, 11:44 AM, "DiFrango, Ronald" <ronald.difra...@capitalone.com> wrote: 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

Re: CPU Utilization: log4j 2.6 and great

s://docs.oracle.com/javacomponents/jmc-5-4/jfr- > runtime-guide/run.htm#JFRUH176>? > This should help diagnose what is going on. > > Remko > > > > On Mon, Feb 13, 2017 at 9:59 PM, DiFrango, Ronald < > ronald.difra...@capitalone.

CPU Utilization: log4j 2.6 and great

All, We recently upgrade to 2.6 and noticed a dramatic increase in CPU and Thread utilization that seems to be tied to the new “garbage free” mode of log4j 2.6. Here’s some of the baseline numbers: · Log4j 2.5: CPU typically ran around 25% · Log4j 2.6: CPU typically ran

Re: Log4J 2.5 -> 2.6 Upgrade NoSuchMethodError

; >On Tue, May 31, 2016 at 3:41 PM, DiFrango, Ronald < >ronald.difra...@capitalone.com> wrote: > >> Paul, >> >> >> I hadn’t seen that before, that would be great! >> >> Ron DiFrango >> >> >> >> >> >> >> &g

Re: Log4J 2.5 -> 2.6 Upgrade NoSuchMethodError

same. > >Cheers, >Paul > >On Tue, May 31, 2016 at 3:37 PM, DiFrango, Ronald < >ronald.difra...@capitalone.com> wrote: > >> Gary, >> >> It ended up being a transitive dependency conflict, one of the included >> libraries had 2.5. >> >> Ron DiFrang

Re: Log4J 2.5 -> 2.6 Upgrade NoSuchMethodError

Gary, It ended up being a transitive dependency conflict, one of the included libraries had 2.5. Ron DiFrango On 5/31/16, 3:38 PM, "DiFrango, Ronald" <ronald.difra...@capitalone.com> wrote: >Gary, > >I did a full clean and install via Maven, but I’ll double

Re: Log4J 2.5 -> 2.6 Upgrade NoSuchMethodError

Gary, I did a full clean and install via Maven, but I’ll double check the dependencies. Thanks, Ron On 5/31/16, 3:35 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote: >On Tue, May 31, 2016 at 11:42 AM, DiFrango, Ronald < >ronald.difra...@capitalone.com> w

Log4J 2.5 -> 2.6 Upgrade NoSuchMethodError

All, I just attempted to upgrade from log42j version 2.5 to 2.6 and I started getting the following: java.lang.NoSuchMethodError: org.apache.logging.log4j.Logger.debug(Ljava/lang/String;Ljava/lang/Object;)V This seems to happen on log messages where we do something simple like: