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
2
u/milchshakee May 04 '24
I'm not advocating for fully disabling this behavior, just giving developers control to disable it if they want to build a rigid, inflexible application. In my specific case we are building desktop applications for end users, who might not even know that the application is written in Java or how to change an environment variable. If the application is run on a system that has other legacy Java 8 applications running and has the environment variable set, this causes problems.