ByteExceptionM commented on issue #3511: URL: https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2694898695
Hey, @vy! I applied the workaround by setting: `LOG4J_STATUS_ENTRIES=0`. At first, it seemed to work fine. The server has been running for **about 8 hours** without any issues, and I didn't see any `ConcurrentLinkedQueue` in the heap summary. However, around **30 minutes ago**, it **suddenly started growing again**. As you can see in the new screenshot, `ConcurrentLinkedQueue$Node` is once again the top memory consumer, and the instance count keeps increasing.  1. Could there be another part of Log4j still using `ConcurrentLinkedQueue`? 2. Is it possible that `LOG4J_STATUS_ENTRIES=0` isn't taking effect properly? (Is there a way I can verify at runtime that Log4j actually applied this setting?) 3. Are there any other Log4j components that may be responsible for this behavior? The second screenshot I uploaded earlier shows how bad this issue got yesterday, reaching **13.9 GB of retained memory** just from these objects. I'll keep monitoring the system, but any further ideas or suggestions would be greatly appreciated! Thanks again! -- 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
