[ https://issues.jboss.org/browse/WFCORE-985?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFCORE-985. ------------------------------------- Resolution: Won't Fix I don't foresee us fixing this. This is because the VM configures java.util.logging before the WildFly process has a chance to see the --properties param and parse the file. The properties that affect the logging behavior have to be passed via -D, either on the command line or via domain.conf. To improve this we'd have to either: 1) Detect --properties in domain.sh | domain.ps1, open and parse the file in the script and pass -D to the VM launch. We're not going to do this. 2) Strip the .sh | .ps1 scripts down to almost nothing and launch a small "launcher" process that in turn has all the logic currently in the scripts, and in turn launches the regular process currently launched by the scripts. The launcher process could then deal with --properties. It's possible (not IMHO probable) we'll do the launcher process some day, and if we do we can revisit this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)