Re: Do we need two leading $ signs for lookups inside XML elements and one $ inside XML attributes?

2018-01-03 Thread Behrang Saeedzadeh
Thanks for the clarification Ralph. Best regards, Behrang Saeedzadeh On 4 January 2018 at 13:27, Ralph Goers wrote: > When the configuration is read all variables are resolved, so every > variable with a single $ will be replaced with its value. When a variable > needs to be resolved at run tim

Re: Do we need two leading $ signs for lookups inside XML elements and one $ inside XML attributes?

2018-01-03 Thread Ralph Goers
When the configuration is read all variables are resolved, so every variable with a single $ will be replaced with its value. When a variable needs to be resolved at run time you must use 2 $ characters. The first will be stripped off leaving the variable reference. That property will then be ev

Add custom message serializer for JsonLayout

2018-01-03 Thread Franz Wong
Hi, I tried to add a custom message serializer for JsonLayout. But it keeps using the default "MessageSerializer". So how can I create a custom message serializer? Thanks. -Franz Here is my code "JsonObjectMessage" @JsonSerialize(using = JsonObjectMessageSerializer.class) public class JsonObj

Do we need two leading $ signs for lookups inside XML elements and one $ inside XML attributes?

2018-01-03 Thread Behrang Saeedzadeh
>From the docs, $$ inside the element: 1. 2. 3. %d %p %c{1.} [%t] $${env:USER} %m%n 4. 5. Also from the docs, $ inside the header attribute: 1. 2. 3. %d %m%n 4. 5. I just read the docs on property substitution and how StrLookup treat variables with mul

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

2018-01-03 Thread Matt Sicker
Those are system properties, but in log4j 2.10+, you can also use an environment variable instead. On 3 January 2018 at 07:36, Fröstl, Christian < [email protected]> wrote: > Hi, > > Thanks, that clarifies it. ( > Is it possible to set the log4j2.asyncQueueFullPolicy and > log4j2.

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

2018-01-03 Thread Fröstl , Christian
Hi, Thanks, that clarifies it. ( Is it possible to set the log4j2.asyncQueueFullPolicy and log4j2.discardThreshold in the log4j2 xml configuration file or only as environment variable? Greetings, Christian On 03.01.18, 09:43, "Remko Popma" wrote: No, the default async queue full policy

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

2018-01-03 Thread Remko Popma
No, the default async queue full policy is to block and not drop any events. (This is different from Logback whose AsyncAppender is “lossy by default if 80% full”.) Log4j 2.10 will block until space becomes available in the buffer. If you configure the DiscardingAsyncQueueFullPolicy (https://l

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

2018-01-03 Thread Fröstl , Christian
Hi, Thanks for your response. Just one question to verify. In the default configuration, all events of level info, debug and trace will be dropped, if the ringbuffer is full. For all other events the application will block and if the ringbuffer has space again, the block will release and the ev