ramanathan1504 commented on issue #2726:
URL:
https://github.com/apache/logging-log4j2/issues/2726#issuecomment-3161324092
Thanks for the quick response!
I originally noticed this while reviewing the available lookups in Log4j2
and got curious about ${jvmrunargs} — mainly for completeness and tooling use.
You’re right that in modern frameworks like Spring Boot, most CLI or JVM args
get surfaced via environment abstractions or system properties, so this lookup
might not add much there.
That said, I’ve worked on some legacy projects (including older Java
Applet-based systems) where we had to tweak and inspect JVM-level arguments
directly — especially for things like agent loading, memory flags, or debug
switches. In those scenarios, being able to dynamically log or inspect JVM run
args at runtime was helpful for monitoring and debugging.
I’m happy to wire up the missing JMX_SINGLETON so the lookup returns
expected values, or alternatively help document its current limitations. Let me
know which direction you’d prefer — I can open a PR if this seems worth fixing.
--
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
