1 of 1 people found this helpful
No, the configuration file name isn't reliably logged.
It's unreliably logged in the server log if 1) Oracle JDK 7 is used (perhaps others do something similar) and 2) you don't use the default config file and instead use the -c switch on the command line. Then you get a full dump of system properties at DEBUG, including:
sun.java.command = /Users/bstansberry/dev/jbossas/bootstrap/jboss-as/build/target/wildfly-8.0.1.Final-SNAPSHOT/jboss-modules.jar -mp /Users/bstansberry/dev/jbossas/bootstrap/jboss-as/build/target/wildfly-8.0.1.Final-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/Users/bstansberry/dev/jbossas/bootstrap/jboss-as/build/target/wildfly-8.0.1.Final-SNAPSHOT -Djboss.server.base.dir=/Users/bstansberry/dev/jbossas/bootstrap/jboss-as/build/target/wildfly-8.0.1.Final-SNAPSHOT/standalone -c standalone-full.xml
You can get better information through the CLI:
[standalone@localhost:9990 /] /core-service=server-environment:read-attribute(name=config-file)
"outcome" => "success",
"result" => "/home/brian/dev/jbossas/jboss-as/build/target/wildfly-8.0.1.Final-SNAPSHOT/standalone/configuration/standalone-full.xml"
Please note though that "Web Profile" and "Full Profile" aren't formal concepts in the software and looking at the config file name only provides a rough estimate as to whether a config supports a particular EE profile. We ship some config files people can use and we certify EE full and web profile compliance. But people can take our standard config files and alter them as they see fit, create something complete different from what we certified with, and still call the file standalone-full.xml.
Mostly you would see in logs that some extra subsystems are being started, subsystems as such would be messaging & jacorb.
you can also customize configuration to only include subsystems you need, that way you don't need to worry about what config you are running.
There is also one other option, but this is highly internal implementation detail and can change at any point in future.
you could look up system property "jboss.server.default.config" that will hold name of the configuration file server was started with, but again, that is internal impl so use it with caution.
The jboss.server.default.config system property is used to set the default config file to use if the -c / --server-config switch isn't used. It doesn't hold the name of the config file actually used.
The idea is you can set -Djboss.server.default.config=standalone-full-ha.xml in standalone.conf once and then save yourself typing -c standalone-full-ha.xml every time you start the server.
Thank you for the information