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 Chainsaw.
On
;Matt Sicker" 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
wrote:
> All,
>
> We’re in the EST/EDT timezone and
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
HH:mm:ss,s
18, 2017, at 2:09 PM, DiFrango, Ronald
wrote:
>
> Laurent,
>
> We had several problems:
>
> 1) We had two different roll-over strategies,
> a. One being time based with no time specified, therefore the file rolled
over every hour
>
les
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: log4j 2.6 and great
Ralph,
S
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
Defaul
> On Feb 14, 2017, at 8:28, Apache wrote:
>
> 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
> ch...@christopherschultz.net> wrote:
> >
> > 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 th
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 sti
ly, 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, DiFrango, R
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 <
DiFrango
On 2/13/17, 11:44 AM, "DiFrango, Ronald" 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 sure that
we’ve seen is that in 2.6.2
/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.com> wrote:
>
> > All,
>
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 arou
Thanks…found it and switching over to it now.
Ron DiFrango
On 5/31/16, 4:44 PM, "Paul Benedict" wrote:
>Refer to the Bill of Material section (BOM) here:
>https://logging.apache.org/log4j/2.x/maven-artifacts.html
>
>Cheers,
>Paul
>
>On Tue, May 31, 20
;
>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 DiFrango
>>
>>
>>
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" wrote:
>Gary,
>
>I did a full clean and install via Maven, but I’ll double check the
>dependenc
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" wrote:
>On Tue, May 31, 2016 at 11:42 AM, DiFrango, Ronald <
>ronald.difra...@capitalone.com> wrote:
>
>> All,
&g
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:
logger.debug(“
19 matches
Mail list logo
