#310 Unable to Set Empty Environment Variable

[Sven Haag]

Set empty environment property in wrapper.conf:

set.EMPTY_TEST_ENTRY=

Check in JAVA application if property exists:

System.getenv().containsKey("EMPTY_TEST_ENTRY")

The property is not there, but it should.
Tested under Windows 10, JDK 1.8.0_144

[Sven Haag]

Enabling debug shows this line at some point:

----C | EMPTY_TEST_ENTRY=<null>

[Maxime Andrighetto]

Thank you for reporting this issue.

Normally Windows won't let you set an empty environment variable (if you do it via the control panel).
According to the Windows c API, setting an empty value should remove the variable from the environment, which I guess is what the Wrapper is doing (although the variable appears in the dump).

I would like to better understand your scenario. Could you please explain why you need to set the variable to an empty value?

Best Regards,

Maxime

[Sven Haag]

Thanks for pointing this out.
My goal is to set an application configuration property to an empty string. The app config can (also) be changed via environment properties. The usual way, of course, would be to use wrapper.java.additional, but in my case I like to explicitly test the environment config mechanisms.
Cheers