This content has been marked as final.
Show 3 replies
-
1. Re: Can we use a different conf file other than standalone.conf
jaysensharma Dec 14, 2015 11:53 PM (in response to arnab_ghosh)Hello Arnab,
If you notice the standalone.sh then you will find that it uses "RUN_CONF" variable to determine which standalone.conf file it need to be used.
--- snippet from standalone.sh ---
# Read an optional running configuration file if [ "x$RUN_CONF" = "x" ]; then RUN_CONF="$DIRNAME/standalone.conf" fi if [ -r "$RUN_CONF" ]; then . "$RUN_CONF" fi
So if you want to use some other file instead like "my_standalone.conf" then set the "RUN_CONF" variable to point to that file.
Example:
$ export RUN_CONF=/NotBackedUp/my_standalone.conf $ cd /PATH/TO/wildfly-8.2.1.Final/bin $ ./standalone.sh
You will find that the memory arguments or other parameters defined in the file "/NotBackedUp/my_standalone.conf " are taking effect.
Regards
Jay SenSharma
-
2. Re: Can we use a different conf file other than standalone.conf
arnab_ghosh Dec 15, 2015 12:07 AM (in response to jaysensharma)Ahh. Thanks Jay. I will try and let you know how it goes.
Regards
Arnab
-
3. Re: Can we use a different conf file other than standalone.conf
arnab_ghosh Dec 15, 2015 3:49 PM (in response to jaysensharma)It is working. Thanks.
Regards
Arnab