Re: [PR] Gradle: Add `buildSrc` to the sample project [logging-log4j-samples]

2025-07-14 Thread via GitHub
ppkarwasz commented on PR #350: URL: https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3069913098 Hi @MartyIX, Thanks again for digging into this — even negative results are valuable, as they help us identify what might be missing in the test project. Based

Re: [PR] Bump org.apache.logging.log4j:log4j-bom from 2.25.0 to 2.25.1 [logging-log4j-audit-sample]

2025-07-14 Thread via GitHub
github-actions[bot] merged PR #81: URL: https://github.com/apache/logging-log4j-audit-sample/pull/81 -- 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: not

[PR] Bump org.apache.logging.log4j:log4j-bom from 2.25.0 to 2.25.1 [logging-log4j-audit-sample]

2025-07-14 Thread via GitHub
dependabot[bot] opened a new pull request, #81: URL: https://github.com/apache/logging-log4j-audit-sample/pull/81 [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.logging.log4j:log4j-bom&package-manager=m

Re: [I] Missing property in the log4j-parent pom file in version 2.25.0 [logging-log4j2]

2025-07-14 Thread via GitHub
MartyIX commented on issue #3779: URL: https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3069541792 I created https://github.com/apache/logging-log4j-samples/pull/350 but anyone who understand Gradle better than is likely needed to finish it. -- This is an automated messa

[PR] Gradle: Add `buildSrc` to the sample project [logging-log4j-samples]

2025-07-14 Thread via GitHub
MartyIX opened a new pull request, #350: URL: https://github.com/apache/logging-log4j-samples/pull/350 This is an attempt to add `buildSrc` for https://github.com/apache/logging-log4j2/issues/3822 to address https://github.com/apache/logging-log4j2/issues/3779#issuecomment-3064916603.

Re: [I] Using log4j-to-slf4j in a web application incorrectly sets a value in a ThreadLocal in org.apache.logging.slf4j.SLF4JLogger [logging-log4j2]

2025-07-14 Thread via GitHub
gmiscione commented on issue #3819: URL: https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3069416278 Code looks ok and now the ThreadLocal is properly gated. Thank you! -- This is an automated message from the Apache Git Service. To respond to the message, please log o

Re: [I] Using log4j-to-slf4j in a web application incorrectly sets a value in a ThreadLocal in org.apache.logging.slf4j.SLF4JLogger [logging-log4j2]

2025-07-14 Thread via GitHub
ppkarwasz commented on issue #3819: URL: https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3069173172 > I don't know if Logback has support for something similar to this pooling that can help in similar cases. Logback does **not** support object pooling in this contex

[PR] fix: Prevent `LogBuilder` memory leak in Log4j API to Logback bridge [logging-log4j2]

2025-07-14 Thread via GitHub
ppkarwasz opened a new pull request, #3824: URL: https://github.com/apache/logging-log4j2/pull/3824 This change fixes a potential memory leak in the `log4j-to-slf4j` module (Logback Log4j API binding) caused by the use of a thread-local `LogBuilder` pool. The leak occurred because th

Re: [I] v3.1.0 does not allow empty file names anymore for RollingFileAppender (logging-log4net)

2025-07-14 Thread via GitHub
mordio commented on issue #260: URL: https://github.com/apache/logging-log4net/issues/260#issuecomment-3069116897 FYI: I am using `.NET Framework v4.8` for the project using log4net. So I can confirm it works for that version. -- This is an automated message from the Apache Git Service.

Re: [I] Using log4j-to-slf4j in a web application incorrectly sets a value in a ThreadLocal in org.apache.logging.slf4j.SLF4JLogger [logging-log4j2]

2025-07-14 Thread via GitHub
gmiscione commented on issue #3819: URL: https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3068154118 I am no expert in low latency programming, but the use case you are describing makes perfect sense. I don't know if Logback has support for something similar to this poolin