There are several options to collect JVM arguments of WildFly application server from the Command Line.
In general terms, if you want to check JVM arguments of a Java process, you can use the 'jps' tool which is available in the 'bin' folder of the JDK. Example:
jps -lvm
8239
-Djboss.server.base.dir=/home/jboss/wildfly-preview/standalone -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED -Dorg.jboss.boot.log.file=/home/francesco/jboss/wildfly-preview/standalone/log/server.log -Dlogging.configuration=file:/home/francesco/jboss/wildfly-preview/standalone/configuration/logging.properties
Also, you can use the jcmd command to get the same information:
jcmd pid VM.system_properties
On the other hand, from the Command Line Interface you can query the platform-mbean node to get the JVM start up arguments:
[standalone@localhost:9990 /] /core-service=platform-mbean/type=runtime:read-attribute(name=input-arguments)
{
"outcome" => "success",
"result" => [
"-D[Standalone]",
"-Xms64m",
"-Xmx512m",
"-XX:MetaspaceSize=96M",
"-XX:MaxMetaspaceSize=256m",
"-Djava.net.preferIPv4Stack=true",
"-Djboss.modules.system.pkgs=org.jboss.byteman",
"-Djava.awt.headless=true",
"--add-exports=java.base/sun.nio.ch=ALL-UNNAMED",
"--add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED",
"--add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED",
"-Dorg.jboss.boot.log.file=/home/francesco/jboss/wildfly-preview/standal
one/log/server.log",
"-Dlogging.configuration=file:/home/francesco/jboss/wildfly-preview/stan
dalone/configuration/logging.properties"
]
}