[jboss-jira] [Red Hat JIRA] (WFCORE-3307) Parameters passed to standalone.sh are not printed on startup

Parameters passed to standalone.sh are not printed on startup ------------------------------------------------------------- Key: WFCORE-3307 URL: https://issues.redhat.com/browse/WFCORE-3307 Project: WildFly Core Issue Type: Enhancement Components: Scripts Affects Versions: 3.0.3.Final, 8.0.0.Beta5 Environment: linux / windows Reporter: jamie smith Assignee: James Perkins Priority: Minor Parameters passed to standalone.sh should also be printed on startup (like JAVA_OPTS). Actually I think something like the output of `ps aux | grep "org.jboss.as.standalone"` should also be printed, when jboss starts. Not printing them causes confusion between what is printed and what is actually applied. If for example someone runs this: `standalone.sh -Djboss.socket.binding.port-offset=100` and at the same time `-Djboss.socket.binding.port-offset=0` exists in JAVA_OPTS, then the latter will be printed but the first will be used. Someone might argue about setting only JAVA_OPTS before running standalone.sh. The reason I avoid setting JAVA_OPTS is that if I set them before running standalone.sh, then the default Wildfly opts (-Djava.net.preferIPv4Stack=true" -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true") are never used, which causes other problems. This could be a bug byitself, but for now I consider it as expected behaviour. So the most clean approach that I see for setting options in a single place (both with -D and custom flags (e.g. -b)) is appending them as params to standalone.sh (e.g. inside a wrapper script myapp-run.sh). It should be possible however to be able to see them being printed somewhere.