[
https://issues.jboss.org/browse/AS7-1849?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-1849:
----------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Alpha1)
Priority: Minor (was: Major)
This is pretty minor. I'll gladly accept a patch.
This basically means if the user passes an undocumented property to domain.sh and gets odd
results, they shouldn't do that. The solution is to track properties that come in from
the command line separately from those that come in from domain.xml/host.xml and if the
former contain any of these jboss.server.xxx properties, filter them out from what gets
passed on to the server VM. ModelCombiner.getServerLaunchCommand() can probably do the
filtering as it processes environment.getHostSystemProperties().
Domain reflects jboss.server.xy properties
------------------------------------------
Key: AS7-1849
URL:
https://issues.jboss.org/browse/AS7-1849
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Scripts
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Priority: Minor
Fix For: 7.1.0.CR1
Domain reflects jboss.server.xy properties, tested with jboss.server.log.dir property.
The same server.log file is used for both server-one and server-two. Only file boot.log
is created in domain/servers/server-one/log and domain/servers/server-two/log directory.
In my case file server.log contains log only for server-one, there is no log for
server-two.
I think jboss.server.xy properties shouldn't be reflected in domain instances.
Even structure of
https://docs.jboss.org/author/display/AS71/Command+line+parameters
implies that jboss.server.xy properties are used for Standalone.
Reproducer of my steps:
{code}
rm -rf domain/servers
bin/domain.sh -Djboss.server.log.dir=/tmp/
ls -aR domain/servers/server-one/log
ls -aR domain/servers/server-two/log
ls -l /tmp/server*
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira