Re: [PR] Bump actions/setup-java from 4.6.0 to 4.7.0 [logging-log4j-samples]
ppkarwasz merged PR #269: URL: https://github.com/apache/logging-log4j-samples/pull/269 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.springframework.cloud:spring-cloud-dependencies from 2024.0.0 to 2024.0.1 [logging-log4j-samples]
ppkarwasz merged PR #295: URL: https://github.com/apache/logging-log4j-samples/pull/295 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Memory Usage Increase in Log4j2 2.24.3 with Async Logging Due to RingBufferLogEvent [logging-log4j2]
ppkarwasz commented on issue #3569: URL: https://github.com/apache/logging-log4j2/issues/3569#issuecomment-2749100490 Hi @shaonan666, `RingBufferLogEvent` does not have a fixed retained size and can gain weight in time if all [garbage-free logging options](https://logging.apache.org/log4j/2.x/manual/garbagefree.html) are enabled. This is due to the fact that **reusable** objects are reused instead of being garbage-collected. A retained size of 744 is nothing alarming. You should check the following options: - [`log4j2.enableThreadlocals`](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.enableThreadlocals) enables GC-free logging. - If GC-free mode is enabled [`log4j2.messageFactory`](https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.messageFactory) defaults to `ReusableMessageFactory` and a `StringBuilder` with variable size (from 128 to 518) is used, as shown by your graphs. - If you additionally enable [`log4j2.garbagefreeThreadContextMap`](https://logging.apache.org/log4j/2.x/manual/garbagefree.html#log4j2.garbagefreeThreadContextMap) each log event will retain and reuse an instance of `SortedArrayStringMap`, which also appears in your graphs. > [!NOTE] > Log4j uses a fuzzy-matching algorithm to match both the official spelling of the configuration properties and some obsolete spellings. You should look if your configuration properties have names **similar** to those above, that start with `log4j` or `org.apache.logging`. -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.logging:logging-parent from 11.3.0 to 12.0.0 [logging-log4j-samples]
ppkarwasz merged PR #272: URL: https://github.com/apache/logging-log4j-samples/pull/272 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump spring-boot.version from 3.4.3 to 3.4.4 [logging-log4j-samples]
ppkarwasz commented on PR #298: URL: https://github.com/apache/logging-log4j-samples/pull/298#issuecomment-2748134640 @dependabot rebase -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump org.apache.logging:logging-parent from 11.3.0 to 12.0.0 in /log4j-samples-graalvm [logging-log4j-samples]
ppkarwasz merged PR #273: URL: https://github.com/apache/logging-log4j-samples/pull/273 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.android.library from 8.8.0 to 8.8.1 in /log4j-samples-android [logging-log4j-samples]
ppkarwasz commented on PR #274: URL: https://github.com/apache/logging-log4j-samples/pull/274#issuecomment-2748132455 @dependabot recreate -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Memory Usage Increase in Log4j2 2.24.3 with Async Logging Due to RingBufferLogEvent [logging-log4j2]
shaonan666 opened a new issue, #3569: URL: https://github.com/apache/logging-log4j2/issues/3569 ## Description I am using Log4j2 in my project and recently upgraded from version 2.23.1 to 2.24.3. The application employs an asynchronous logging strategy with Disruptor version 3.4.3. Below is the relevant configuration: - `log4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector` - `log4j2.asyncQueueFullPolicy=org.apache.logging.log4j.core.async.DiscardingAsyncQueueFullPolicy` - `log4j2.discardThreshold=ERROR` - `log4j2.asyncLoggerWaitStrategy=Yield` - `log4j2.asyncLoggerRingBufferSize=1048576` The logging frequency in my application is relatively low, averaging about 10 log entries per second. When using version 2.23.1, memory usage remained stable based on monitoring data . However, after upgrading to 2.24.3, I observed a gradual increase in memory usage over time, which eventually stabilizes at a fixed threshold.  This behavior differs significantly from what I experienced with 2.23.1. Through heap dump analysis at different time intervals, I confirmed that the memory growth is primarily associated with `RingBufferLogEvent` objects within Log4j2’s RingBuffer implementation, with the RingBuffer’s memory footprint consistently increasing over time.    I noticed that the 2.24.3 release includes several changes related to memory management. Could any of these changes, particularly those affecting the RingBuffer or `RingBufferLogEvent`, explain the behavior I am observing? If additional details are needed, please let me know, and I’d be happy to provide them. ## Environment - **Log4j2 Version**: 2.24.3 (upgraded from 2.23.1) - **Disruptor Version**: 3.4.3 - **JVM**: Zing24.08.101.0+1 (build 21.0.4.0.101+1-LTS) - **Logging Frequency**: ~10 logs/second -- 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...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] logj4 3.0.0.beta3 with JPL + JPMS [logging-log4j2]
ppkarwasz closed issue #3570: logj4 3.0.0.beta3 with JPL + JPMS URL: https://github.com/apache/logging-log4j2/issues/3570 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] StatusData#getFormattedStatus can throw ArrayIndexOutOfBoundsException [logging-log4j2]
vy closed issue #3562: StatusData#getFormattedStatus can throw ArrayIndexOutOfBoundsException URL: https://github.com/apache/logging-log4j2/issues/3562 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump com.palantir.javaformat:palantir-java-format from 2.60.0 to 2.61.0 [logging-parent]
github-actions[bot] merged PR #361: URL: https://github.com/apache/logging-parent/pull/361 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix ArrayIndexOutOfBoundsException on StatusData#getFormattedStatus [logging-log4j2]
vy merged PR #3563: URL: https://github.com/apache/logging-log4j2/pull/3563 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix deployment of test artifacts [logging-parent]
ppkarwasz merged PR #360: URL: https://github.com/apache/logging-parent/pull/360 -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Fix deployment of test artifacts [logging-parent]
vy commented on code in PR #360: URL: https://github.com/apache/logging-parent/pull/360#discussion_r2009851760 ## src/changelog/.12.x.x/fix_deployment.xml: ## @@ -0,0 +1,8 @@ + +http://www.w3.org/2001/XMLSchema-instance"; + xmlns="https://logging.apache.org/xml/ns"; + xsi:schemaLocation="https://logging.apache.org/xml/ns https://logging.apache.org/xml/ns/log4j-changelog-0.xsd"; + type="fixed"> + https://github.com/apache/logging-parent/pull/360"/> + Stop deployment of test artifacts. Review Comment: ```suggestion Use the `maven.deploy.skip` Maven property in `nexus-staging-maven-plugin`. This effectively fixes the skipping of test artifacts' deployments. ``` -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
