ViliusS commented on PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#issuecomment-2824475309
> One particular thing that is bothering me about this _fix_ is... it breaks
backward compatibility. We can say we're fixing the schema, but for users who
have already been using t
ppkarwasz closed pull request #322: Bump org.apache.logging.log4j:log4j-bom
from 2.25.0-SNAPSHOT to 3.0.0-beta3 in /log4j-samples-graalvm in the all group
across 1 directory
URL: https://github.com/apache/logging-log4j-samples/pull/322
--
This is an automated message from the Apache Git Serv
ppkarwasz commented on PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#issuecomment-2823876400
> One particular thing that is bothering me about this _fix_ is... it breaks
backward compatibility. We can say we're fixing the schema, but for users who
have already been using
will-zdu commented on issue #3635:
URL:
https://github.com/apache/logging-log4j2/issues/3635#issuecomment-2823808000
com.lmax.disruptor.SleepingWaitStrategy#applyWaitMethod
the default sleepTimeNs to too low，cause the hign cpu usage
--
This is an automated message from the Apache Git S
will-zdu opened a new issue, #3635:
URL: https://github.com/apache/logging-log4j2/issues/3635
## Description
When using Log4j2 in asynchronous logging mode, the CPU usage is
significantly higher than expected, even under low logging throughput. This
issue persists regardless of the c
vy closed issue #3634: slf4j2-impl not published with 3.0.0-beta3
URL: https://github.com/apache/logging-log4j2/issues/3634
--
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 u
vy commented on PR #3586:
URL: https://github.com/apache/logging-log4j2/pull/3586#issuecomment-2823388744
One particular thing that is bothering me about this _fix_ is... it breaks
backward compatibility. We can say we're fixing the schema, but for users who
have already been using the _bro
