GitHub user jbisotti added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Thank you! I appreciate your helpfulness and all your hard work on thi
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
> Also, we intentionally had `log4j-core` as a `compile` dependency b
GitHub user jbisotti edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Apologies; I misspoke yesterday.
We recently added a unit test to ve
GitHub user jbisotti added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Apologies; I misspoke yesterday.
We recently added a unit test to ver
GitHub user ppkarwasz added a comment to the discussion: Badly formatted status
msg in AbstractDriverManagerConnectionSource
Hi @RichMacDonald — great catch! 💯
This issue has actually been present since version `2.22.0` (commit
4c53356bc08a81d374eca42adcfea67aa5384f1e), so thank you for spott
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
> Due to our steps to keep deprecated code out of the codebase, this
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Hi @jbisotti,
Thanks for the feedback regarding version `2.25.1` — m
GitHub user jbisotti added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Adding the two options it's complaining about results in a different f
GitHub user jbisotti edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
To keep deprecated code out of our codebase, we enable deprecation wa
GitHub user jbisotti edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
To keep deprecated code out of our codebase, we enable deprecation wa
GitHub user jbisotti added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
To keep deprecated code out of our codebase, we enable deprecation war
GitHub user ppkarwasz added a comment to the discussion: What are the
differences between the various prefixes in asynchronous loggers?
That’s an excellent question — and one that gets to the heart of Log4j Core’s
architecture.
To answer it properly, we need to distinguish between two key com
GitHub user krystalXfoss added a comment to the discussion: I’m terrified for
humanity’s future
Also I’ve contacted someone who can reach out to the UN about this so it can
hopefully be fixed permanently;
https://x.com/mcraddock/status/1942142163577413788
GitHub link:
https://github.com/apa
GitHub user krystalXfoss added a comment to the discussion: I’m terrified for
humanity’s future
Also I’ve contacted someone who can reach out to the UN about this so it can
hopefully be fixed permanently;
https://x.com/mcraddock/status/1942142163577413788
GitHub link:
https://github.com/apa
GitHub user vy added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
@ZOUG, a `Throwable` is essentially composed of 3 parts:
1. The stack trace (i.e., `StackTraceElement[]`)
2. A cause (of type `Throwable`)
3. The suppressed exceptio
GitHub user ppkarwasz added a comment to the discussion: Roadmap for `2.25.1`
release
The vote to release **Apache Log4j 2.25.1** has started and will remain open
for **72 hours**. We invite the community to test the release candidate to help
ensure a stable and reliable release.
## How to P
GitHub user ZOUG added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
You are right on this. There is indeed one related issue that is a potential
bug though. When I tried `%xEx{5}`, the depth level is ignored and the stack
trace is
GitHub user ZOUG edited a comment on the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(includin
GitHub user ZOUG edited a comment on the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(includin
GitHub user ZOUG added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
I was considering to move to `log4j2` from `logback`, whose default behavior
for `%ex{5}` is printing 5 lines of stack trace for **each exception level
(including
GitHub user vy added a comment to the discussion: Exception causes are
truncated while logging exceptions with line number limit
@ZOUG, if cause is crucial for your case, can you use `%rEx{5}` instead? If
not, how do you expect Log4j to render your stack trace given you only want to
see 5 lin
GitHub user BinayakThakur added a comment to the discussion: Exception causes
are truncated while logging exceptions with line number limit
Hey @ZOUG , This sounds more like feature and less like bug
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3803#discussioncomment-136
GitHub user i-make-robots edited a comment on the discussion: Log4j creates an
empty log file and refuses to fill it?
Whoops.
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3793#discussioncomment-13636074
This is an automatically sent email for dev@logging.apache.org.
GitHub user i-make-robots added a comment to the discussion: Log4j creates an
empty log file and refuses to fill it?
Whoops.Sent from my iPhoneOn Jul 1, 2025, at 11:54 AM, Piotr P. Karwasz
***@***.***> wrote:
Hi @i-make-robots,
My Java 22 open source project is
https://github.com/Marginally
GitHub user ppkarwasz added a comment to the discussion: Log4j creates an empty
log file and refuses to fill it?
Hi @i-make-robots,
> My Java 22 open source project is
> [https://github.com/MarginallyClever/Makelangelo-software/](https://github.com/MarginallyClever/Makelangelo-software/).
>
GitHub user martinRocks added a comment to the discussion: Support for template
names
I have tried it. It seems to get me what I need in the json, however, the
console still blows up with the error. My next step is to test it with splunk.
However, I have to wait for my IT guys to get that
GitHub user FreeAndNil added a comment to the discussion: Support for template
names
Have you tried your solution?
You can easily exchange the PatternLayout with your own layout in the log4net
configuration:
https://logging.apache.org/log4net/manual/configuration/layouts.html
In case you log
GitHub user i-make-robots edited a discussion: Log4j creates an empty log file
and refuses to fill it?
Hello, everyone. I hope you're doing well.
My Java 22 open source project is
https://github.com/MarginallyClever/Makelangelo-software/.
I'm using logback and log4j with a rolling file app
GitHub user martinRocks added a comment to the discussion: Support for template
names
What do you think about doing something like this? I'm not sure if any of the
names are something that my cloud log reader would ingest, but that should fix
part of my problem. To make this work, just add t
GitHub user francolawpaybyphone closed a discussion: Log4net stopped sending
logs to datadog agentless logging
Hey,
I just noticed that my application stopped sending logs to datadog using direct
agentless logging.
Wondering if that has happened before or if anyone else has any insights?
I sa
GitHub user FreeAndNil added a comment to the discussion: Support for template
names
There are some possibilities:
You can
- derive your own `LoggingEvent`
- override `RenderedMessage` and `WriteRenderedMessage` (with your special
format logic)
- derive your own logger
- override `ForcedLog`
GitHub user martinRocks added a comment to the discussion: Support for template
names
Thank you so very much for the detailed and quick response. I have an idea on
how to get it to work. If it works, I will share what I have with you.
However, there is still the problem of the StringFormat
GitHub user ppkarwasz added a comment to the discussion: Getting current
date-time format (or default format)
> First of all, thank you for answering 🙂 Second, regarding your first comment
> (i didn't want to quote it) is't not up for the user to decide how the time
> will be formatted, I'm t
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
See #3789
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3788#discussioncomment-13604535
This is an automatically sent email for dev@logging.apache.org.
To unsu
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
First of all, thank you for answering 🙂
Second, regarding your first comment (i didn't want to quote it) is't not up
for the user to decide how the time will be formatted, I'm the one wh
GitHub user ppkarwasz added a comment to the discussion: Getting current
date-time format (or default format)
If you chose the `-MM-dd HH:mm:ss,SSS` format because it was one of the few
formats optimized for low garbage generation by `FixedDateFormat`, it's worth
noting that this limitati
GitHub user ppkarwasz added a comment to the discussion: Getting current
date-time format (or default format)
You might consider a different approach to keep the date format consistent
between your application output and Log4j logs.
Here’s a flexible strategy:
1. **Define a shared default fo
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that return
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
Yes, certainly right now I execute the following code:
```java
private static final DateTimeFormatter DATE_TIME_FORMATTER =
DateTimeFormatter.ofPattern(
FixedDateFor
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
Yes, certainly right now I execute the following code:
```java
private static final DateTimeFormatter DATE_TIME_FORMATTER =
DateTimeFormatter.ofPattern(
FixedDateFor
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
Yes, certainly right now I execute the following code:
```java
private static final DateTimeFormatter DATE_TIME_FORMATTER =
DateTimeFormatter.ofPattern(
FixedDateForm
GitHub user ppkarwasz added a comment to the discussion: Getting current
date-time format (or default format)
> I'm not trying to introspect anything, but I do `println` (in addition to
> logs) some data I got from `HttpClient` and I'm printing dates (as
> Last-Modified) with the default patt
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that return
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that return
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that return
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that return
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
in addition, why can't all the named patterns be an enum with 3 fields (base
pattern, compact postfix and non-compact postfix) and a getter with `boolean
compact` parameter that returns
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
by the way, I've noticed that in
`org.apache.logging.log4j.core.pattern.DatePatternConverter#decodeNamedPattern`,
inside the switch-case `case "DEFAULT"`, you're using it again instead
GitHub user ashr123 edited a comment on the discussion: Getting current
date-time format (or default format)
I'm not trying to introspect anything, but I do `println` (in addition to logs)
some data I got from `HttpClient` and I'm printing dates (as Last-Modified)
with the default pattern cau
GitHub user ashr123 added a comment to the discussion: Getting current
date-time format (or default format)
I'm not trying to introspect anything, but I do `println` (in addition to logs)
some data I got from `HttpClient` and I'm printing dates (as Last-Modified)
with the default pattern caus
GitHub user ppkarwasz added a comment to the discussion: Getting current
date-time format (or default format)
Thanks for the question!
Could you tell us more about your use case? For example, are you trying to
introspect the effective Log4j Core configuration at runtime, or are you
attemptin
GitHub user FreeAndNil added a comment to the discussion: Support for template
names
Thanks for the detailed explanation and the sample app.
I believe there might be a misunderstanding regarding how log4net handles
message templates. The kind of structured logging you're describing (e.g.,
us
GitHub user martinRocks added a comment to the discussion: Support for template
names
Thank you for the quick reply. I have created a small demo app for how I have
things configured. If I have anything set wrong, please let me know. I hope
this helps explain my problem. I am surprised tha
GitHub user FreeAndNil added a comment to the discussion: Support for template
names
I am not aware of a possible solution to your problem.
@gdziadkiewicz do you have an idea?
GitHub link:
https://github.com/apache/logging-log4net/discussions/261#discussioncomment-13599719
This is an au
GitHub user martinRocks edited a discussion: Support for template names
When will log4net allow the use of template names? For example, a log message
like this:
```_log.InfoFormat("Started {time}", DateTime.Now);```
so that the message comes out in Json format like this:
```
{
"date": "2025-
GitHub user alexsuter added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Tried to making work with `tycho-compiler-plugin`. Did not find any s
GitHub user alexsuter added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
This works. Thanks!
GitHub link:
https://github.com/apache/logging-
GitHub user ppkarwasz edited a discussion: Roadmap for `2.25.1` release
Hi everyone,
@vy and I had a call to discuss the aftermath of the `2.25.0` release. While
generally successful, we identified a few issues that affect usage in specific
environments. To address these promptly, we're plann
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
I'm not a Tycho user, but from what I can tell, the configuration for
GitHub user kwakeroni added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Thank you for taking this into account
GitHub link:
https://github.
GitHub user garydgregory added a comment to the discussion: Roadmap for
`2.25.1` release
>From my POV, I use Jetty, Spring Boot and Spring Batch (😀
>https://www.manning.com/books/spring-batch-in-action) for one project, so it's
>good to see 2.25.1 is planned for a July release.
GitHub link:
GitHub user garydgregory edited a comment on the discussion: Roadmap for
`2.25.1` release
>From my POV, I use Jetty (which has its own OSGi impl), Spring Boot and Spring
>Batch (😀 https://www.manning.com/books/spring-batch-in-action) for one
>project, so it's good to see 2.25.1 is planned for
GitHub user ppkarwasz added a comment to the discussion: Roadmap for `2.25.1`
release
### 🛠️ Additional Issue: Spring Boot Compatibility
`2.25.0` introduced a regression that affects integration with **Spring Boot**
([[#3770](https://github.com/apache/logging-log4j2/issues/3770)](https://gith
GitHub user ppkarwasz edited a comment on the discussion: Roadmap for `2.25.1`
release
### 🛠️ Additional Issue: Spring Boot Compatibility
`2.25.0` introduced a regression that affects integration with **Spring Boot**
(#3770):
* For historical reasons, Spring Boot uses `LoggerContext.start(Co
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Thank you for your feedback!
You're absolutely right — we hadn’t ful
GitHub user kwakeroni added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
I agree. I have no annotation processors configured in my pom, all ru
GitHub user THausherr added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Thank you! I also suggest that the log4j documentation be updated, wi
GitHub user THausherr added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Thank you! It builds successfully now. I see you also made a (slightl
GitHub user ratoaq2 added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
It seems a bit cumbersome for a project that has nothing to do with Gra
GitHub user ratoaq2 edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
It seems I got it working with proc none plus empty annotation proces
GitHub user ratoaq2 added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
the proc none didn't seem to work for me...
It seems I got it working
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
@THausherr,
I couldn't reproduce your problems with PDFBox. I submit
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Nice catch! :100:
Somehow `only` ended up in my example, which disabl
GitHub user ppkarwasz edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Hi @ratoaq2,
Thanks for the detailed error log — it's very helpful.
GitHub user THausherr edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
I tried the last change with default-compile and now the project tha
GitHub user THausherr added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
I tried the last change with default-compile and now the project that
GitHub user ppkarwasz edited a comment on the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Hi @ratoaq2,
Thanks for the detailed error log — it's very helpful.
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Hi @ratoaq2,
Thanks for the detailed error log — it's very helpful.
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Hi @kwakeroni,
There’s **no dedicated flag** to turn `GraalVmProcess
GitHub user THausherr added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
```
org.apache.maven.plugins
maven-co
GitHub user ppkarwasz added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
The warning in the release notes warning is a simplified explanation
GitHub user THausherr added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
Same for me with Apache PDFBox. What I noticed is that it works when
GitHub user ftreede added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
It is automatically registered via META-INF services. So the only way t
GitHub user ratoaq2 edited a discussion: java.lang.IllegalArgumentException:
The `GraalVmProcessor` annotation processor is missing the required
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options
Hi all,
I have a java 21 maven project which uses eclipse compiler
org.codehaus.plex
GitHub user kwakeroni added a comment to the discussion:
java.lang.IllegalArgumentException: The `GraalVmProcessor` annotation processor
is missing the required `log4j.graalvm.groupId` and `log4j.graalvm.artifactId`
options
I have the same issue.
The release notes say "the processor will fail
GitHub user ratoaq2 edited a discussion: java.lang.IllegalArgumentException:
The `GraalVmProcessor` annotation processor is missing the required
`log4j.graalvm.groupId` and `log4j.graalvm.artifactId` options
Hi all,
I have a java 21 maven project which uses eclipse compiler
org.codehaus.plex
GitHub user FreeAndNil added a comment to the discussion: Log4net stopped
sending logs to datadog agentless logging
It depends how you define silently.
The app won't crash on logging errors.
See https://logging.apache.org/log4net/manual/faq.html#internal-debugging
GitHub link:
https://github.
GitHub user francolawpaybyphone added a comment to the discussion: Log4net
stopped sending logs to datadog agentless logging
Does log4net fail silently?
GitHub link:
https://github.com/apache/logging-log4net/discussions/254#discussioncomment-13498828
This is an automatically sent email
GitHub user francolawpaybyphone added a comment to the discussion: Log4net
stopped sending logs to datadog agentless logging
The problem was resolved by redeploying the application. APM metrics and the
application were working fine at the time. Only logs were not sent.
GitHub link:
https://g
GitHub user francolawpaybyphone added a comment to the discussion: Log4net
stopped sending logs to datadog agentless logging
Yes we can consider updating to log4net 3.1.0
I could not reproduce the issue
I have also created a support ticket to Datadog
GitHub link:
https://github.com/apache/log
GitHub user FreeAndNil edited a comment on the discussion: Log4net stopped
sending logs to datadog agentless logging
Could you please update log4net to 3.1.0? 2.x is no longer supported.
I don’t see any clear connection between your logging configuration and Datadog.
Can you clarify how this wo
GitHub user francolawpaybyphone edited a comment on the discussion: Log4net
stopped sending logs to datadog agentless logging
log4net version - 2.0.15
config file looks something like this -
```xml
```
extensions - log4net.Ext.Json
[Datado
GitHub user francolawpaybyphone edited a comment on the discussion: Log4net
stopped sending logs to datadog agentless logging
log4net version - 2.0.15
config file looks something like this -
```xml
```
extensions - l
GitHub user FreeAndNil added a comment to the discussion: Log4net stopped
sending logs to datadog agentless logging
Could you please update log4net to 3.1.0? 2.x is no longer supported.
I don’t see any clear connection between your logging configuration and Datadog.
Can you clarify how this iss
GitHub user francolawpaybyphone added a comment to the discussion: Log4net
stopped sending logs to datadog agentless logging
log4net version - 2.0.15
config file looks something like this -
`
`
extensions - log4net.Ext.J
GitHub user FreeAndNil added a comment to the discussion: Log4net stopped
sending logs to datadog agentless logging
Hi @francolawpaybyphone,
we need a lot more details to help you.
- What version of log4net are you using?
- How does your config-file look like?
- Do you use any extension for l
GitHub user vy added a comment to the discussion: Attribute 'additivity' is not
allowed to appear in element 'Logger'
> Because of these limitations, XML validation errors in Log4j configuration
> files should be taken with a grain of salt
@ppkarwasz, this is a very nice and elaborate respons
GitHub user ppkarwasz added a comment to the discussion: Attribute 'additivity'
is not allowed to appear in element 'Logger'
Hi @jorge683,
Yes, this is indeed a bug — tracked here: apache/logging-log4j-tools#135 — in
the [Log4j Docgen
tool](https://logging.apache.org/log4j/tools/log4j-docgen
GitHub user ppkarwasz added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
> But can you think of scenarios where this may occur ?
In version `2.21.0`, the parameter formatting logic was changed to **strictly
enforce** a match between `{}` place
GitHub user arbardhan added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
2.24.3 is not available under our org enterprise distribution yet - pending
approval. We only go back to older versions. But can you think of scenarios
where this may occ
1 - 100 of 182 matches
Mail list logo
