Re: [PR] Bump version to 1.3.0 [logging-log4cxx]

swebb2066 commented on PR #365: URL: https://github.com/apache/logging-log4cxx/pull/365#issuecomment-2041863687 Benchmark results on Windows 11 VS2022 comparing v1.2.0.json to v1.3.0.json | Benchmark | Time | CPU | Time Old | Time New | CPU Old | CPU New | | --- | - | |

Re: [PR] Bump version to 1.3.0 [logging-log4cxx]

swebb2066 commented on PR #365: URL: https://github.com/apache/logging-log4cxx/pull/365#issuecomment-2041833640 Benchmark results on Ubuntu gcc 11.4 comparing v1.2.0.json to v1.3.0.json |Benchmark |Time |CPU |Time Old |Time New |CPU Old |CPU New | | | | -- | --- | ---

[PR] Bump version to 1.3.0 [logging-log4cxx]

swebb2066 opened a new pull request, #365: URL: https://github.com/apache/logging-log4cxx/pull/365 (no comment) -- 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 unsubscri

Re: [PR] Improve instructions for building log4cxx [logging-log4cxx]

swebb2066 merged PR #364: URL: https://github.com/apache/logging-log4cxx/pull/364 -- 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-unsubscr

Re: [PR] Improve release process repeatability [logging-log4cxx]

swebb2066 merged PR #363: URL: https://github.com/apache/logging-log4cxx/pull/363 -- 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-unsubscr

Re: [PR] Improve instructions for building log4cxx [logging-log4cxx]

swebb2066 commented on code in PR #364: URL: https://github.com/apache/logging-log4cxx/pull/364#discussion_r1555146356 ## src/site/markdown/development/build-cmake.md: ## @@ -22,28 +22,82 @@ Building with CMake {#build-cmake} --> [TOC] -## Quick start: +# Supported options

Re: [PR] Improve instructions for building log4cxx [logging-log4cxx]

swebb2066 commented on code in PR #364: URL: https://github.com/apache/logging-log4cxx/pull/364#discussion_r1555146356 ## src/site/markdown/development/build-cmake.md: ## @@ -22,28 +22,82 @@ Building with CMake {#build-cmake} --> [TOC] -## Quick start: +# Supported options

Re: [PR] Improve instructions for building log4cxx [logging-log4cxx]

swebb2066 commented on code in PR #364: URL: https://github.com/apache/logging-log4cxx/pull/364#discussion_r1555144938 ## src/site/markdown/4-build.md: ## @@ -21,9 +21,17 @@ Build {#build} limitations under the License. --> +As of version 0.11.0, the only supported build sy

Re: [PR] Improve instructions for building log4cxx [logging-log4cxx]

rm5248 commented on code in PR #364: URL: https://github.com/apache/logging-log4cxx/pull/364#discussion_r1555094695 ## src/site/markdown/development/build-cmake.md: ## @@ -22,28 +22,82 @@ Building with CMake {#build-cmake} --> [TOC] -## Quick start: +# Supported options -

Re: [I] Threads contention because of OutputStreamManager.writeBytes (logging-log4j2)

bharathchandrathakkallapally-cpi commented on issue #2447: URL: https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041407219 @tcmot yes, all the servers in the cluster are facing this issue. There is no problem with the hard drive or IO, we had the AWS guy checked our quota

Re: [I] Threads contention because of OutputStreamManager.writeBytes (logging-log4j2)

tcmot commented on issue #2447: URL: https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041371880 Are all servers like this? Is there a problem with the hard drive? If there is no deadlock, it is likely that data cannot be written to the hard drive. @bharathchandrath

Re: [I] Lambda expressions compiled with a previous version of `org.apache.logging.log4j.util.Supplier.java` or `MessageSupplier` fail to generate (logging-log4j2)

ritzow closed issue #2449: Lambda expressions compiled with a previous version of `org.apache.logging.log4j.util.Supplier.java` or `MessageSupplier` fail to generate URL: https://github.com/apache/logging-log4j2/issues/2449 -- This is an automated message from the Apache Git Service. To resp

Re: [I] Threads contention because of OutputStreamManager.writeBytes (logging-log4j2)

bharathchandrathakkallapally-cpi commented on issue #2447: URL: https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041354023 @tcmot according the thread dump analysis we did, there is no deadlock. @jvz If it is related to the rollover, this issue should be only seen a

Re: [I] Lambda expressions compiled with a previous version of `org.apache.logging.log4j.util.Supplier.java` or `MessageSupplier` fail to generate (logging-log4j2)

ritzow commented on issue #2449: URL: https://github.com/apache/logging-log4j2/issues/2449#issuecomment-2041349748 @ppkarwasz I think I may have found a sneaky bug with a change you made. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[I] Lambda expressions compiled with a previous version of `org.apache.logging.log4j.util.Supplier.java` or `MessageSupplier` fail to generate (logging-log4j2)

ritzow opened a new issue, #2449: URL: https://github.com/apache/logging-log4j2/issues/2449 ## Description I believe that adding `extends java.util.function.Supplier` to `log4j-api/src/main/java/org/apache/logging/log4j/util/Supplier.java` may have caused binary or source code incomp