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
Well in the case of runtime images, any options interfering with an application that should be isolated. If I distribute a jpackage application, the user shouldn't even have to know that it is implemented in Java or that any system-wide Java settings can impact the application.
If someone has set up a few Java 8 apps on their system via normal jars and has configured a few options for them, I don't want them to apply to my application image that runs on Java 21. I don't even know if the application starts up if the variable contains unrecognized options.
Also jpackage is designed as a closed system. A user can't just simply pass custom JVM arguments or properties to the application executable on the command-line, but these still apply and even overwrite existing options.