Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is it possible to set an environment variable at runtime from Java?

Is it possible to set an environment variable at runtime from a Java application? In Java 1.5 java.lang.System class there is the getenv() method, I would only need a setenv() method...

Is it possible to modify the environment variables in the java process itself; not in the child process.

Is it possible to achieve it through JNI? And how would that work?

Thanks.

EDIT: Ok let me put it this way - Can we do the following with Java. Please answer.

  1. Can we modify the environment of the current process?
  2. Can we modify the environment of the parent process?
  3. Can we modify the environment of the child process?

Hemal Pandya has answered that "You can modify the environment of current and child processes but not of the parent process that spawned this process." Do you agree with this ?

like image 851
Vicky Avatar asked Feb 24 '09 01:02

Vicky


People also ask

Can environment variables be changed at runtime?

Env vars are intentionally private to each process. So unless the program provides an API for changing its env vars you can't modify them once the program is running.

What is runtime environment variable?

Using runtime environment variables. Runtime environment variables are key/value pairs deployed alongside a function. These variables are scoped to the function and are not visible to other functions in your project.

Do we need to set environment variables for JRE?

If you're using the installer we'll do this part for you. If you installed the Java Development Kit (JDK) you'll be setting the JAVA_HOME environment variable. If you installed the Java Runtime Environment (JRE) you will follow the same steps but set the JRE_HOME environment variable instead.


2 Answers

If my intuition is correct, and you actually want to modify the environment for the benefit of a spawned (forked) sub-process (Runtime.getRuntime().exec()), then use ProcessBuilder instead of exec(). You can build a custom environment via your ProcessBuilder instance's environment() method.

If this is not what you are trying to achieve then kindly disregard this answer.


UPDATE

The answer to your three updated, specific questions is as follows:

  1. Can we modify the environment of the current process?
    • Not easily. Depends whether you want to change the process' environment, to change the value(s) returned by System.getenv() in the same JVM, or both.
    • As Greg Hewgill pointed out, to change the current process' environment you can call setenv or its platform-specific equivalent via JNI. You may also employ the extremely convoluted method from point 2 below, which works for any process (provided you have the permissions.) However, be aware that in most JVMs this change might never be reflected in the values returned by System.getenv(), as the environment is more often than not cached at virtual machine startup in a java.util.Map (or equivalent.)
    • To change the JVM's cached copy of the environment, when a cache is used (see the source code in System.java in whichever JVM distribution you will be using to deploy), you may try hacking the implementation (via class loading order, reflection, or instrumentation.) In the case of SUN's v1.6 JVM, for example, the environment cache is managed by the undocumented ProcessEnvironment class (which you can patch.)
  2. Can we modify the environment of the parent process?
    • Extremely difficult, and highly non-portable. If you absolutely and imperatively have to, there are very specific hacks that you can employ:
      • Windows: Dynamically Add/Edit Environment variables of Remote process
      • *nix: Is there a way to change another process’s environment variables? -- this is a performance killer, as any process instrumented by gdb will be suspended for a non-zero amount of time.
  3. Can we modify the environment of the child process?
    • Yes, through ProcessBuilder when spawning the process.
    • If the process has already been spawned when the environment alteration is required, you need method 2 above (or some equally convoluted method, such as code-injection at spawn time, ulteriorly controlled through e.g. socket by the parent process.)

Note that all methods above, except for the one involving ProcessBuilder, are brittle, error prone, non-portable to various degrees, and prone to race conditions in multi-threaded environments.

like image 100
vladr Avatar answered Sep 18 '22 18:09

vladr


You can get a handle on the underlying map that java.lang.ProcessEnvironment is holding on to, and then put new stuff and remove stuff all you want.

This works on java 1.8.0_144. Can't guarantee it works on any other version of java, but it's probably similar if you really need to change the environment at run time.

private static Map<String,String> getModifiableEnvironment() throws Exception{     Class pe = Class.forName("java.lang.ProcessEnvironment");     Method getenv = pe.getDeclaredMethod("getenv");     getenv.setAccessible(true);     Object unmodifiableEnvironment = getenv.invoke(null);     Class map = Class.forName("java.util.Collections$UnmodifiableMap");     Field m = map.getDeclaredField("m");     m.setAccessible(true);     return (Map) m.get(unmodifiableEnvironment); } 

After you get the reference to the map, just add whatever you want and you can now retrieve it using the regular old System.getenv("") call.

I tried this its working in MAC not working in Windows in both os java version 1.8_161

like image 37
Snowbuilder Avatar answered Sep 20 '22 18:09

Snowbuilder