vy commented on issue #3511: URL: https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2701176267
> I applied the workaround by setting: `LOG4J_STATUS_ENTRIES=0` @ByteExceptionM, can you explain what do you exactly mean by applying this setting? Do you pass this as an environment variable to the associated `java` process? Would it be possible to share a heap dump with us? If so, you can 1. [OPTIONAL] encrypt<sup>1</sup> the heap dump, 2. upload it somewhere publicly reachable, and 3. send an email to `priv...@logging.apache.org` on where to download and how to unpack. <sup>1</sup> You can encrypt it either using a password-protected ZIP, or via GPG. In the latter case, you need [public keys of Log4j maintainers](https://downloads.apache.org/logging/KEYS). -- 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
