[jboss-jira] [JBoss JIRA] (WFLY-9367) Parameters passed to standalone.sh are not printed on startup

[kobogian hitis (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kobogian hitis updated WFLY-9367:
---------------------------------
    Description: 
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.





  was:
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 `-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.







> Parameters passed to standalone.sh are not printed on startup
> -------------------------------------------------------------
>
>                 Key: WFLY-9367
>                 URL: https://issues.jboss.org/browse/WFLY-9367
>             Project: WildFly
>          Issue Type: Bug
>          Components: Scripts
>    Affects Versions: 10.1.0.Final
>         Environment: linux / windows
>            Reporter: kobogian hitis
>            Assignee: Tomaz Cerar
>            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.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)