github-actions[bot] merged PR #2562:
URL: https://github.com/apache/logging-log4j2/pull/2562
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
AndreKurait commented on issue #2169:
URL:
https://github.com/apache/logging-log4j2/issues/2169#issuecomment-2094011204
Hi,
I'm seeing this with 2.23.1 and Disruptor 4.0.0 in my application.
It's happening when i use
```
--
This is an automated message from the Apache Git Ser
github-actions[bot] merged PR #2564:
URL: https://github.com/apache/logging-log4j2/pull/2564
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
github-actions[bot] closed pull request #2565: Bump
org.apache.commons:commons-csv from 1.10.0 to 1.11.0
URL: https://github.com/apache/logging-log4j2/pull/2565
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093782558
This was just a simple war deployment. I imagine it would be the same in
other app servers but I'm not 100% to be honest.
* `-Dlog4j.configurationFile=...` def
ppkarwasz commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093749449
> 4. I used jconsole which seemed to show two separate sets of MBeans,
and I used jmap to get some hierarchies which both seemed to indicate that
indeed these are loade
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093657272
@ppkarwasz I did a little playing around, and here's what I found.
1. I set the two system properties you mentioned, and found I got two stack
traces, similar
ppkarwasz commented on issue #2026:
URL:
https://github.com/apache/logging-log4j2/issues/2026#issuecomment-2093550469
@yvasyliev,
I am closing this issue then, since it works in `3.x` and we can not port it
to `2.x` (due to the JDK 8 baseline).
--
This is an automated message from
ppkarwasz closed issue #2026: Add record support for @Plugin annotation
URL: https://github.com/apache/logging-log4j2/issues/2026
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
ppkarwasz commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093509213
@marcreichman-pfi,
You can check which class creates a logger context by setting the
`-Dog4j2.loggerContextStacktraceOnStart=true` and `-Dlog4j2.debug` system
proper
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093399662
@ppkarwasz I did a little digging, and noticed that even on a fresh
deployment, there are multiple descriptors to these files. I found an
interesting java agent
[he
yvasyliev commented on issue #2026:
URL:
https://github.com/apache/logging-log4j2/issues/2026#issuecomment-2093398592
`3.0.0-beta2` works OK with Java records.
[Source code](https://github.com/yvasyliev/log4j2-demo)
Output:
```
Hello, World!
```
--
This is an automa
marcreichman-pfi commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093320241
@ppkarwasz Thanks for your response. I would have told you that for sure
there are not multiple applications referencing the configuration, but `lsof`
is bringing in
ppkarwasz commented on issue #2566:
URL:
https://github.com/apache/logging-log4j2/issues/2566#issuecomment-2093307679
@marcreichman-pfi,
Are you by any chance using the same configuration in multiple web
applications? On Linux you can check with
[`lsof`](https://linux.die.net/man/8/
marcreichman-pfi opened a new issue, #2566:
URL: https://github.com/apache/logging-log4j2/issues/2566
## Description
In *some* cases (this is intermittent) it seems that when a log file
(synchronous appender) is being written to by several threads at once, it can
get into a situation whe
github-actions[bot] closed pull request #2563: Bump guava.version from
33.1.0-jre to 33.2.0-jre
URL: https://github.com/apache/logging-log4j2/pull/2563
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go t
github-actions[bot] merged PR #173:
URL: https://github.com/apache/logging-parent/pull/173
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
ppkarwasz commented on issue #2525:
URL:
https://github.com/apache/logging-log4j2/issues/2525#issuecomment-2092569941
The following documentation changes were applied:
- [ ] #2552
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
ppkarwasz merged PR #2552:
URL: https://github.com/apache/logging-log4j2/pull/2552
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubsc
ppkarwasz commented on issue #2558:
URL:
https://github.com/apache/logging-log4j2/issues/2558#issuecomment-2092443502
@rgoers,
So it seems that the most uniform way to provide passwords is to either
provide them literally or use a lookup?
Should we deprecate `PasswordDecryptor
20 matches
Mail list logo
