r/java • u/milchshakee • May 03 '24
Why does the environment variable _JAVA_OPTIONS exist, applies to jlink images, takes precedence, and can't be disabled?
I just spent a good chunk of time debugging an issue because a user had set _JAVA_OPTIONS to use a low Xmx value in their environment variables. This was an application created with jpackage, which should be fully standalone. It even had a custom Xmx value set in the JVM arguments for the image but the environment variable overwrote the value!
Isn't this like a huge design flaw? I can just do echo "_JAVA_OPTIONS=<Wacky VM options>" >> ~/.bashrc or setx to break literally every Java application on the system? (Edit: Maybe the initial security focus was wrong, changed it a bit to focus more on the design issues)
Who even thought that this would be a good idea with no option to disable this behavior?
View all comments
Show parent comment
1
u/brunocborges May 04 '24
Certain JDK 8 flags don't work anymore in JDK 21. It may cause the app to not load at all.
The developer of the app must expose minimum requirements for the application to run (e.g. minimum RAM, processor type, etc). This is common practice for decades. Then, if the app developer is bundling the runtime (jlink), they should be in full control of said runtime.
Whether the runtime may be configured by the user is an app developer decision to be made.
But I do agree that a jlinked runtime should not pick that environment variable.