Re: Apache chainsaw

You need to use the new home.apache.org site for uploading things now anyways. Who knows how long they'll keep the old server online. If we set it up in Jenkins, we can also have snapshots published to Nexus. On 29 March 2017 at 14:53, Ralph Goers wrote: > We can’t

Re: Apache chainsaw

We can’t be pointing people to use snapshots from your personal page. I’m not even sure how you can publish there any more. Can’t you do a release if there are features that you use? It would be nice to at least say it supports Log4j 2 and how to set it up. Ralph > On Mar 29, 2017, at 12:30

Re: Re[2]: Apache chainsaw

Shouldn't we set up a Jenkins job for this so people can get snapshots? Also, would be a good idea to work on a release at some point before another decade happens without anyone noticing! :) On 29 March 2017 at 14:30, Scott Deboy wrote: > I use it and it works well for

Re: Re[2]: Apache chainsaw

I use it and it works well for logs under 1M records, assuming you can give the JVM enough memory. I use the developer snapshot here: https://people.apache.org/~sdeboy/ On 3/29/17, João Ferreira wrote: > Yeah, that was what i expected. But is there any project

Re: Apache chainsaw

https://logging.apache.org/chainsaw/changes-report.html Last Published: 09/01/2007 I'd say it's not active. Igal Sapir Lucee Core Developer Lucee.org On 3/29/2017 11:56 AM, João Ferreira wrote: Hello, Is apache chainsaw still an active project? If not, was it replaced by

Apache chainsaw

Hello, Is apache chainsaw still an active project? If not, was it replaced by another project? Best regards Joao

Re: Kafka Appender with Programmatic Configuration

Oh, I see. That's an interesting API... On 29 March 2017 at 10:49, Marvin Geitner wrote: > Thank you very much, > > kafkaBuilder.addComponent(builder.newComponent("bootstrap.servers", > "Property", "kafka.host:*9092*")); > > is working. > > BR > Marvin > >

Re: About performance

Pietro, The performance impact of logging location information is massive. See https://logging.apache.org/log4j/2.x/performance.html#asyncLoggingWithLocation You can increase logging speed by ~80x by not logging location information. If you follow the conventions that each class has its own

AW: Kafka Appender with Programmatic Configuration

Thank you very much, kafkaBuilder.addComponent(builder.newComponent("bootstrap.servers", "Property", "kafka.host:*9092*")); is working. BR Marvin -Ursprüngliche Nachricht- Von: Ralph Goers [mailto:ralph.go...@dslextreme.com] Gesendet: Mittwoch, 29. März 2017 17:46 An: Log4J Users

Re: Kafka Appender with Programmatic Configuration

Mikael’s solution is correct. Every item in the ConfigurationBuilder is a Component. We have “special” Components for things that are always used, such as Loggers and Appenders. But we can’t know about every type of Component so in those cases you just use the generic Component. Ralph > On

Re: About performance

What Java version are you using? Why do you think your code is going to perform better than what Log4j is doing? The fastest way to get the caller information is to use Java 9’s StackWalker.getCallerClass() method which only takes a couple of milliseconds. But doing that might actually make

Re: Kafka Appender with Programmatic Configuration

But it would be nice to have a simpler way to do that. On Wed, Mar 29, 2017 at 5:28 PM, Mikael Ståldal wrote: > Have you tried this: > > kafkaBuilder.addComponent(builder.newComponent("bootstrap.servers", > "Property", "kafka.host:*9092*")); > > > On Wed, Mar 29,

Re: Kafka Appender with Programmatic Configuration

Have you tried this: kafkaBuilder.addComponent(builder.newComponent("bootstrap.servers", "Property", "kafka.host:*9092*")); On Wed, Mar 29, 2017 at 5:26 PM, Matt Sicker wrote: > Looks like a bug to me! Here's the issue: a Properties component is > injected into a kafka

Re: Kafka Appender with Programmatic Configuration

Looks like a bug to me! Here's the issue: a Properties component is injected into a kafka appender, but there is no way to create a Property or Properties component directly via the configuration builder API. The top level properties aren't injected in the kafka appender (and manager), so they're

Re: About performance

The %m%n pattern is just the formatted message and a new line. The %M pattern is for method names. And the current algorithm for finding it is about the same: <

Kafka Appender with Programmatic Configuration

Hi all, I'm trying to configure the Kafka Appender with the programmatic configuration described in the manuals. So I created the ConfigurationFactory and set up the AppenderComponentBuilder. If I execute the Application I'll get following exception: Caused by:

About performance

Hi, sorry for boothering you all. I'm in the need to have a logging optimization and i whould like to ask you all about the use of %m%n. Due to the fact i need optimization should i use : %m%n or should implement my own Class/Method name finder with: private static String getLoggingMethod()