I think this is not supported, but basically you can do two things to bring in your environment variables:
Use System.setProperty before Log4J gets configured
Convert (your) environment variables to system properties in your launcher
The first option basically boils down to this:
for (Map<String,String>.Entry entry : System.getenv().entrySet()) {
System.setProperty(entry.getKey(), entry.getValue());
}
... but the question is of course where to put this code. In particular if you're running within some sort of Tomcat container or similar, this might be troublesome.
The other largely depends on your environment. Basically if you have a shell script that starts your app, you can write some shell magic to set all environment variables as properties, or just the ones you need, e.g.:
java -DMY_ENV=$MY_ENV -DMY_OTHER_ENV=$MY_OTHER_ENV -cp ... com.example.Main
It's also possible to alter your server startup scripts to support this, e.g. catalina.sh or similar.