Re: Async logger not logging after upgrading tomcat, jdk and log4j

Log4j is concerned, our upcoming 3.0.0-beta2 will feature a separate `log4j-async-logger` artifact with a non-optional dependency on `com.lmax.disruptor:disruptor`[3]. We hope to relieve users from the burden of upgrading the Disruptor library themselves and rely on the transitive dependency in `log4j

RE: Async logger not logging after upgrading tomcat, jdk and log4j

: Async logger not logging after upgrading tomcat, jdk and log4j Hi Joan, On Thu, 25 Jan 2024 at 12:06, wrote: > My application has been using async logging for years by setting this env > variable on tomcat 8.5.x running on java 11 with log4j-2.15/6/7/8/9: > -DLog4jContex

RE: Async logger not logging after upgrading tomcat, jdk and log4j

org.apache.logging.log4j2:type=55494dde,component=Appenders,name=DefaultConsole-2 Joan. -Original Message- From: joan.balagu...@ventusproxy.com Sent: Thursday, January 25, 2024 1:56 PM To: 'Log4J Users List' Subject: RE: Async logger not logging after upgrading tomcat, jdk and log4j Hello, Here

RE: Async logger not logging after upgrading tomcat, jdk and log4j

Hello, Here is the trace when starting tomcat with '-Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector': https://gist.github.com/joanbalaguero/1fa286417bfc9dbd3ce75e043bd26f3d It seems the async contexts are started, but maybe someone can see something

RE: Async logger not logging after upgrading tomcat, jdk and log4j

To: Log4J Users List Subject: Re: Async logger not logging after upgrading tomcat, jdk and log4j Hello, Check the dependency hierarchy, which version of log4j is being used. I had faced similar issue, even though if I specified some particular version of log4j, maven was not picking

RE: Async logger not logging after upgrading tomcat, jdk and log4j

Hi Piotr, I already did it ... no success. Thanks, Joan. -Original Message- From: Piotr P. Karwasz Sent: Thursday, January 25, 2024 1:20 PM To: Log4J Users List Subject: Re: Async logger not logging after upgrading tomcat, jdk and log4j Hi Joan, On Thu, 25 Jan 2024 at 12:06

Re: Async logger not logging after upgrading tomcat, jdk and log4j

Hi Joan, On Thu, 25 Jan 2024 at 12:06, wrote: > My application has been using async logging for years by setting this env > variable on tomcat 8.5.x running on java 11 with log4j-2.15/6/7/8/9: > -DLog4jContextSelector=org.apache.logging.log4j.core.async.BasicAsyncLoggerContextSelector > > Now

Re: Async logger not logging after upgrading tomcat, jdk and log4j

Hello, Check the dependency hierarchy, which version of log4j is being used. I had faced similar issue, even though if I specified some particular version of log4j, maven was not picking that particular version though there were no other dependencies which were using log4j at any nested level.

Async logger not logging after upgrading tomcat, jdk and log4j

Hello, I would like to ask about this issue before starting to post debug logs. My application has been using async logging for years by setting this env variable on tomcat 8.5.x running on java 11 with log4j-2.15/6/7/8/9:

Async logger context selector creates a throwable in JSON layout

Hello, I'm currently migrating our codebase to Log4j2 (2.9.1) in a Tomcat 9.0.7 environment, and while testing different configurations I noticed a weird, what i think also undocumented, difference between the standard usage and when starting with -DLog4jContextSelector=org.apa

Re: [External] Re: Log4j2 Async logger fallback method

gt; QykinLq8RJFWq5YIigJq8wWizXFOxKy3DWeXTomCnaM= >> > >> >(Shameless plug) Every java main() method deserves >> https://urldefense.proofpoint.com/v2/url?u=http-3A__picocli. >> info=DwIFaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU

Re: [External] Re: Log4j2 Async logger fallback method

8TE=hk-mti7hK6agTdNqpiQVl3gpA4ri4hrn2pxHf_8maIE= >> QykinLq8RJFWq5YIigJq8wWizXFOxKy3DWeXTomCnaM= >> > >> >(Shameless plug) Every java main() method deserves >> https://urldefense.proofpoint.com/v2/url?u=http-3A__picocli. >> inf

Re: [External] Re: Log4j2 Async logger fallback method

w2x7qWvjFgf1pKLN7kb5Q534FwglDl16TI5-OArl4= > >> On Dec 20, 2017, at 2:03, Fröstl, Christian < christian.froe...@accenture.com> wrote: >> >> Hi, >> >> I currently don’t find any documentation regarding the fallback methods of the log4j2 async l

Re: [External] Re: Log4j2 Async logger fallback method

info=DwIFaQ=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU= > 37nF0SnGtdjmcblOpYG7cKwaPDc1GWo5GNDvnDLF8TE=hk- > mti7hK6agTdNqpiQVl3gpA4ri4hrn2pxHf_8maIE=w_ > w2x7qWvjFgf1pKLN7kb5Q534FwglDl16TI5-OArl4= > > > >> On Dec 20, 2017, at 2:03, Fröstl, Christian < > christian.froe.

Re: [External] Re: Log4j2 Async logger fallback method

röstl, Christian <christian.froe...@accenture.com> wrote: >> >> Hi, >> >> I currently don’t find any documentation regarding the fallback methods of the log4j2 async logger. >> What happens when the AsyncLogger.RingBufferSize is too smal

Re: [External] Re: Log4j2 Async logger fallback method

glDl16TI5-OArl4= > >> On Dec 20, 2017, at 2:03, Fröstl, Christian >> <christian.froe...@accenture.com> wrote: >> >> Hi, >> >> I currently don’t find any documentation regarding the fallback methods of >> the log4j2 async logger. >> What

Re: [External] Re: Log4j2 Async logger fallback method

.@accenture.com> wrote: > > Hi, > > I currently don’t find any documentation regarding the fallback methods of the log4j2 async logger. > What happens when the AsyncLogger.RingBufferSize is too small to log all entries from a burst? Will the application fa

Re: Log4j2 Async logger fallback method

java main() method deserves http://picocli.info > On Dec 20, 2017, at 2:03, Fröstl, Christian <christian.froe...@accenture.com> > wrote: > > Hi, > > I currently don’t find any documentation regarding the fallback methods of > the log4j2 async

Log4j2 Async logger fallback method

Hi, I currently don’t find any documentation regarding the fallback methods of the log4j2 async logger. What happens when the AsyncLogger.RingBufferSize is too small to log all entries from a burst? Will the application fall back into sync logging and slow down the application or will the new

Re: Question about async logger wait strategies

If the sources have not been moved, it's still considered as experimental on master (and it was still experimental on 3.3.5-rc2 tag) https://github.com/LMAX-Exchange/disruptor/blob/master/src/main/java/com/lmax/disruptor/LiteBlockingWaitStrategy.java 2016-06-14 7:15 GMT+02:00 Gary Gregory

Re: Question about async logger wait strategies

On Mon, Jun 13, 2016 at 9:51 PM, Anthony Maire wrote: > Basically you want a logging framework to have as little impact as possible > on the application. That's why the sleeping strategy is a good > general-purpose choice : no allocation, no lock for the application >

Re: Question about async logger wait strategies

Basically you want a logging framework to have as little impact as possible on the application. That's why the sleeping strategy is a good general-purpose choice : no allocation, no lock for the application threads, and a CPU consumption when "idle" that will stay pretty low on most OS (it roughly

Re: Question about async logger wait strategies

Currently there isn't but there's no real reason not to. That reminds me we should add LiteBlocking (a standard Disruptor wait strategy). Sent from my iPhone > On 2016/06/14, at 5:50, Matt Sicker wrote: > > Also, is there a way to specify a custom WaitStrategy, or is that

Re: Question about async logger wait strategies

The busy-spin wait strategy is not something I want to promote since it basically dedicates a full core to the logging background thread. It's there mostly for testing and perhaps for hardcore users who are familiar with the Disruptor. Sent from my iPhone > On 2016/06/14, at 3:24, Matt

Re: Question about async logger wait strategies

Also, is there a way to specify a custom WaitStrategy, or is that pointless? On 13 June 2016 at 13:24, Matt Sicker wrote: > The code has a case for the busy spin strategy, but it's not listed on > this page: . Is > this

Question about async logger wait strategies

The code has a case for the busy spin strategy, but it's not listed on this page: . Is this unsupported or should it be added to the docs? -- Matt Sicker

Re: Async Logger

> > Hi All > > We are using log4j2 in Apache Hive project. We are exploring the option of > using Async Logger. From the doc, > https://logging.apache.org/log4j/2.x/manual/async.html#AllAsync the > requirements for async loggers are the presence of disruptor jar in cla

Re: Async Logger

When you say "enables Async logging", what exactly do you mean? What do you observe? Sent from my iPhone > On 2016/03/16, at 11:08, Prasanth Jayachandran <prasan...@apache.org> wrote: > > Hi All > > We are using log4j2 in Apache Hive project. We are explori

Async Logger

Hi All We are using log4j2 in Apache Hive project. We are exploring the option of using Async Logger. From the doc, https://logging.apache.org/log4j/2.x/manual/async.html#AllAsync the requirements for async loggers are the presence of disruptor jar in classpath and the system property

Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

It may be possible (but a bit of a hack) to use async loggers without reflection. It involves compiling your own version of the com.lmax.disruptor.util.Util class where you replace the implementation of the #getUnsafe() method with a simple call to sun.misc.Unsafe.getUnsafe(). Obviously this is

RE: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

, July 30, 2013 10:14 AM To: Log4J-Users List Subject: Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1 It may be possible (but a bit of a hack) to use async loggers without reflection. It involves compiling your own version of the com.lmax.disruptor.util.Util

RE: async logger on slow single core env performs 50% worse than log4j v1

Hi Remko / log4j2, - Tnx for the correction, I'll retest async logger: System.setProperty(Log4jContextSelector, org.apache.logging.log4j.core.async.AsyncLoggerContextSelector); - Before I recompile with a test run for async logger I'll edit log4j2.xml and add bufferedIO=false

reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

LOGGER.debug(sun.reflect.Reflection is not installed); //  236 -Original Message- From: Remko Popma [mailto:rem...@yahoo.com] Sent: Saturday, July 27, 2013 5:40 AM To: Log4J Users List; Remko Popma Subject: Re: async logger on slow single core env

Re: async logger on slow single core env performs 50% worse than log4j v1

Hang on! By fish tagging do you mean you use logger#entry, #exit, #catching? These methods walk the stack trace to determine the location (class, method) which will give you a *huge* performance penalty! If you#x27;re using async logging this is 20x slower, for sync logging (slower to begin

Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

236 -Original Message- From: Remko Popma [mailto:rem...@yahoo.com] Sent: Saturday, July 27, 2013 5:40 AM To: Log4J Users List; Remko Popma Subject: Re: async logger on slow single core env performs 50% worse than log4j v1 I quickly reviewed

Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

Popma [mailto:rem...@yahoo.com] Sent: Saturday, July 27, 2013 5:40 AM To: Log4J Users List; Remko Popma Subject: Re: async logger on slow single core env performs 50% worse than log4j v1 I quickly reviewed the code and as far as I can tell: * only the following places in Log4j-2 will create

RE: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

) at java.security.AccessController.doPrivileged(AccessController.java:255) ... 40 more -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com] Sent: Monday, July 29, 2013 11:05 AM To: Log4J Users List Subject: Re: reflection? RE: async logger on slow single core env

Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

29, 2013 11:05 AM To: Log4J Users List Subject: Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1 This probably warrants an enhancement to Log4jContextFactory. I can imagine other use cases where defaulting to BasicContextSelector also makes sense

RE: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

the default be the simplest? Is there benefit from me setting: Log4jContextSelector to org.apache.logging.log4j.core.selector.BasicContextSelector. FWIW I'm having to give up on async logger because my VM doesn't support reflection, and unless I'm not understanding this new architecture

Re: reflection? RE: async logger on slow single core env performs 50% worse than log4j v1

is default??? I'm not setting Log4jContextSelector so it has to be using some context, wouldn't the default be the simplest? Is there benefit from me setting: Log4jContextSelector to org.apache.logging.log4j.core.selector.BasicContextSelector. FWIW I'm having to give up on async logger

Re: async logger on slow single core env performs 50% worse than log4j v1

threads or async logging. I'd be interested in your answers to my questions below. Best regards, Remko From: Remko Popma rem...@yahoo.com To: Log4J Users List log4j-user@logging.apache.org Sent: Saturday, July 27, 2013 12:53 PM Subject: Re: async logger on slow

async logger on slow single core env performs 50% worse than log4j v1

I suspect a slow single core env is a new scenario for v2 and async logger. My view is that there's a mis match between v2's async logger thread design that works great on multi-core envs and this embedded slow single core env... Sooo I need to try a few different configurations to see what

RE: async logger on slow single core env performs 50% worse than log4j v1

_ From: SMITH, CURTIS Sent: Friday, July 26, 2013 1:16 PM To: log4j-user@logging.apache.org Subject: async logger on slow single core env performs 50% worse than log4j v1 I suspect a slow single core env is a new scenario for v2 and async logger. My view is that there's a mis

Re: async logger on slow single core env performs 50% worse than log4j v1

the hood vs V1 with: sync Logger and RollingFile. Any guesses for me to try? Tnx curt _ From: SMITH, CURTIS Sent: Friday, July 26, 2013 1:16 PM To: log4j-user@logging.apache.org Subject: async logger on slow single core env performs 50

RE: async logger on slow single core env performs 50% worse than log4j v1

...@dslextreme.com] Sent: Friday, July 26, 2013 5:34 PM To: Log4J Users List Subject: Re: async logger on slow single core env performs 50% worse than log4j v1 I'm curious why you are even trying to use Async anything with a single core environment (unless it is hyper-threaded). Only 1 thread can be active

Re: async logger on slow single core env performs 50% worse than log4j v1

attempts to slim it down It's still 2x worse than v1. Something else is in play. curt -Original Message- From: Ralph Goers [mailto:ralph.go...@dslextreme.com] Sent: Friday, July 26, 2013 5:34 PM To: Log4J Users List Subject: Re: async logger on slow single core env performs 50

Re: async logger on slow single core env performs 50% worse than log4j v1

] Sent: Friday, July 26, 2013 5:34 PM To: Log4J Users List Subject: Re: async logger on slow single core env performs 50% worse than log4j v1 I'm curious why you are even trying to use Async anything with a single core environment (unless it is hyper-threaded). Only 1 thread can be active

Re: async logger on slow single core env performs 50% worse than log4j v1

@logging.apache.org Sent: Saturday, July 27, 2013 6:55 AM Subject: RE: async logger on slow single core env performs 50% worse than log4j v1 LOL well that's obvious now.  :)  It was more a case of wishful thinking and why not give it a try.    But it's still odd that my attempts to slim it down

Confused: want low latency: do I need BOTH async logger AND async appender??

http://logging.apache.org/log4j/2.x/manual/async.html This URL describes that v2 has both async logger and async appender. What is the suggested config for an embedded situation where I want low latency, nothing fancy? I've had do this in code since we don't own the cmd line: OSGi

Re: Confused: want low latency: do I need BOTH async logger AND async appender??

if you hit any snags. Regards, Remko Sent from my iPhone On 2013/07/24, at 0:39, SMITH, CURTIS cs0...@att.com wrote: http://logging.apache.org/log4j/2.x/manual/async.html This URL describes that v2 has both async logger and async appender. What is the suggested config for an embedded