[ https://issues.jboss.org/browse/WFCORE-3909?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3909: ------------------------------------------ This sounds like an RFE to me. It's not a bug that there are differences in how software we write functions. Note that standalone.sh does _not_ work by ensuring that all -D arg are passed as args to java. Most are passed as args to org.jboss.modules.Main, which in turn passes them through to org.jboss.as.server.Main, which in turn sets the system property. Same as the CLI CommandLineMain. This is done well after JVM launch and after quite a lot of system properties are read. IOW if you want to be sure your property is set before it's read, you need to edit standalone.conf. Using -D args to standalone.sh as a way to configure logging definitely doesn't work. Passing properties as args to standalone.sh is actually somewhat an anti-pattern that we support for historical reasons. Having the CLI script process all args and ensure that any -D is passed to java means a lot of script complication that would need to be maintained for all variations. And then, if the requirement is all scripts have the same functionality, that means we have to alter all the other scripts, including standalone.sh, to do the same thing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)