[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Michael Voegele updated AS7-1947: --------------------------------- Description: Starting JBoss using jboss_install/bin/domain.bat -Djboss.home.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_install -Djboss.domain.base.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain -Djboss.domain.config.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain\configuration leads to Unable to read the logging configuration from 'file:C:\eplatform\jboss\AS-7.0-Test\jboss_install/domain/configuration/logging.properties' Options jboss.domain.base.dir / jboss.domain.config.dir are ignored. was: Starting JBoss using _jboss_install/bin/domain.bat -Djboss.home.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_install -Djboss.domain.base.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain -Djboss.domain.config.dir=C:\eplatform\jboss\AS-7.0-Test\jboss_appl_1\domain\configuration leads to Unable to read the logging configuration from 'file:C:\eplatform\jboss\AS-7.0-Test\jboss_install/domain/configuration/logging.properties' Options jboss.domain.base.dir / jboss.domain.config.dir are ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Michael Voegele commented on AS7-1947: -------------------------------------- No, C:\eplatform\jboss\AS-7.0-Test\jboss_install/domain/configuration/logging.properties does not exist. I moved the whole domain folder from jboss_install to jboss_appl_1 (actually jboss_domain_1). I created the file, then it is working. But the log directory (jboss.domain.log.dir = jboss.domain.base.dir/log) is also not recognized. The logs of process-controller and host-controller are placed under jboss_install. These are also hardcoded in domain.bat. So it seems only a matter of cleaning up the scripts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-1947: ------------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda commented on AS7-1947: ---------------------------------------- @The log property won't most likely not be reflected, since the startup script does not understand java properties. AS7-1947 seems to be related to that. (from AS7-1850) boot.log for host-controller and process-controller are created under domain/log because domain.sh/.bat scripts can't reflect java properties. I think there are two ways: * parse arguments within .bat/.bash scripts {code} ## Properties from -D parameter for var in "$@" do echo "$var" if [[ $var == -Djboss.domain.log.dir=* ]]; then echo "OK -- `echo $var | sed 's/-Djboss.domain.log.dir=//'`" fi done {code} {code} ## Properties from file . property_file echo $prop ## but problems with jboss.domain.log.dir :( unusable {code} {code} ## Properties from file for var in `cat test.properties` do echo "$var" if [[ $var == jboss.domain.log.dir=* ]]; then echo "OK -- `echo $var | sed 's/jboss.domain.log.dir=//'`" fi done {code} Something similar should be developed for Windows but I'm not sure if it's possible at all. I checked commands for 'cmd' [1] and I couldn't find something similar to sed. Command findstr can be used as grep substitute. * introduce LOG_PATH + CONFIGURATION_PATH properties as described in AS7-2494 I vote for LOG_PATH + CONFIGURATION_PATH properties [1] http://ss64.com/nt/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-1947: --------------------------------------- If for this fix we're going to end up looping through all the command line params checking for -D, please also change things such that they all become arguments to java instead of arguments to main. (I'm not proposing doing that for properties from file though.) I suspect though that the AS7-2494 approach will win out. For the first approach above, we'd also need to deal with -D values set in standalone.conf/domain.conf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1947?page=com.atlassian.jira.plugin.s... ] Stian Lund commented on AS7-1947: --------------------------------- Downloading the lates snapshot I notice the JBOSS_BASE_DIR is checked for in standalone.sh but not actually used to set the jboss.server.base.dir property. So in any init-script you still have to set -Djboss.server.base.dir=$JBOSS_BASE_DIR . LOG_DIR and CONFIG_DIR works fine though, so thanks to whoever put them in :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira