ByteExceptionM commented on issue #3511: URL: https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2701264737
> > I understand that 2.23.1+ introduced major changes, but I can't simply upgrade to Log4j 2.24.3, because the Minecraft server (or one of its plugins) depends on Log4j **2.22.1**. Unfortunately, I don't have a way to fully track which component is responsible for this dependency, so updating is difficult at the moment. > > Log4j follows semantic versioning, so you can safely upgrade to `2.24.3`. In version `2.23.0` a big refactoring of `StatusLogger` took place, but it did not affect binary compatibility. > > We only maintain the last minor version of each major branch, so there will never be a `2.22.2` release. If this bug does **not** affect `2.24.3`, we might add some note to `2.22.x`, but we will not fix it. My concern is not about compatibility, but about the practical feasibility of upgrading. In my environment, there are multiple software components relying on Log4j 2.22.1, including the Minecraft server itself and various plugins. The issue is that I do not have a clear way to track which components depend on this specific version, and I cannot simply replace or modify the software running my server without thorough testing and validation. This makes upgrading much more complex than just switching the Log4j version in a standalone application. > > I applied the workaround by setting: `LOG4J_STATUS_ENTRIES=0` > > [@ByteExceptionM](https://github.com/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] encrypt1 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. > > 1 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). Yes, I applied the setting by passing it as an environment variable to the Java process: `LOG4J_STATUS_ENTRIES=0`. I can prepare a heap dump and will send it over soon. I'll follow the encryption and upload instructions and notify you via email when it's ready. 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
