MichaelMorrisEst commented on issue #3074:
URL:
https://github.com/apache/logging-log4j2/issues/3074#issuecomment-2446349933
Hi @ppkarwasz
The use case is that when a certificate expires and is replaced that the
SocketAppender can continue without the need for manual intervention (curre
ayhamthemayhem commented on PR #5:
URL: https://github.com/apache/logging-site/pull/5#issuecomment-2446351063
> Why would you skip dormant projects? At some point flume will be coming
back into the fold and I won't want to remember to have to modify this.
>
Hey, dormant projects are n
ayhamthemayhem commented on PR #5:
URL: https://github.com/apache/logging-site/pull/5#issuecomment-2446358385
>Could you also remove Matomo from footer.html and add a reference to your
script to header.html?
done !
--
This is an automated message from the Apache Git Service.
To respo
ayhamthemayhem commented on PR #5:
URL: https://github.com/apache/logging-site/pull/5#issuecomment-2446363147
If there is a list or more info on which websites are dormant or skipped
that would be great.
I would adjust the PR quickly as needed :)
--
This is an automated message from t
kelunik commented on issue #3143:
URL:
https://github.com/apache/logging-log4j2/issues/3143#issuecomment-2446495388
Full reproducer:
https://gist.github.com/kelunik/be51e5e2fdf746bbc86383b922bbb05e
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
github-actions[bot] merged PR #3142:
URL: https://github.com/apache/logging-log4j2/pull/3142
--
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
morvael commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2446421080
`private static Map normalizeProperties(Properties...
propertiesList) {`
returns empty map, so no relevant properties were detected I guess.
--
Thi
morvael commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2446414383
This is the config stack trace:
--
This is an automated message from the Ap
kelunik opened a new issue, #3143:
URL: https://github.com/apache/logging-log4j2/issues/3143
## Description
LoggerContext / LoggerRegistry don't play well together in using weak
references, which can result in a `null` logger if the GC kicks in at a bad
timing.
## Configuratio
ppkarwasz commented on issue #3100:
URL:
https://github.com/apache/logging-log4j2/issues/3100#issuecomment-2446579770
@morvael,
> Ok, it seems I'm going through that code twice actually. And in the second
one I'm doing code-based rebuild of configuration to configure some stuff in
t
morvael closed issue #3100: Unwanted logging by StatusLogger
URL: https://github.com/apache/logging-log4j2/issues/3100
--
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 unsubs
ppkarwasz commented on issue #3074:
URL:
https://github.com/apache/logging-log4j2/issues/3074#issuecomment-2446935514
Hi @MichaelMorrisEst ,
> The spring boot implementation is exactly the type of functionality we are
looking for. We already use this for SSL communication in our code
ppkarwasz commented on issue #3146:
URL:
https://github.com/apache/logging-log4j2/issues/3146#issuecomment-2447288575
Due to #2691 any problems with the throwable converters in `2.24.1`, will no
longer apply to `2.25.0`.
In the current implementation, however, there is an _off-by-one
garydgregory opened a new issue, #3146:
URL: https://github.com/apache/logging-log4j2/issues/3146
## Description
The pattern `%xThrowable{depth}` does not work, for example,
`%xThrowable{2}` and `%xThrowable{99}` both print the same stack trace, which
is also the default stack trace
ppkarwasz commented on issue #3146:
URL:
https://github.com/apache/logging-log4j2/issues/3146#issuecomment-2448097451
> I would like a setting that shows me EVERYTHING, no truncations, but
that's likely a feature request 😉
Isn't that the default behavior of `%throwable`?
--
This i
garydgregory commented on issue #3146:
URL:
https://github.com/apache/logging-log4j2/issues/3146#issuecomment-2447841678
FWIW, my expectation was that the depth counts stack FRAMES, not lines, for
BOTH the exception AND its causes.
--
This is an automated message from the Apache Git Ser
garydgregory commented on issue #3146:
URL:
https://github.com/apache/logging-log4j2/issues/3146#issuecomment-2447844520
I would like a setting that shows me EVERYTHING, no truncations, but that's
likely a feature request 😉
--
This is an automated message from the Apache Git Service.
To
garydgregory commented on issue #3146:
URL:
https://github.com/apache/logging-log4j2/issues/3146#issuecomment-2448156834
Well, no, that's part of the confusion in the docs: "full" and "complete"
corresponds to the default Java (or Log4j? ) behavior which truncates stack
frames and write "2
github-actions[bot] merged PR #3145:
URL: https://github.com/apache/logging-log4j2/pull/3145
--
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
23 matches
Mail list logo
