[
https://issues.jboss.org/browse/WFCORE-350?page=com.atlassian.jira.plugin...
]
John Mazzitelli commented on WFCORE-350:
----------------------------------------
See:
http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html
I would say the solution should involve any properties, not just jboss.server.xxx
properties.
In my case, I'm trying to inject a javaagent into the host controller but I do NOT
want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL)
I'm forced to pass in
"-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and
"-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host
controller can start up.
But these gets passed to the spawned servers and causes them to fail to boot up (because
while my -javaagent command line argument isn't passed to their JVM, the -D sys props
are and those combination of sys props are deadly without a JUL-enabled javaagent).
Domain reflects jboss.server.xy properties
------------------------------------------
Key: WFCORE-350
URL:
https://issues.jboss.org/browse/WFCORE-350
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Rostislav Svoboda
Assignee: ehsavoie Hugonnet
Priority: Minor
Fix For: 3.0.0.Alpha23
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 was sent by Atlassian JIRA
(v7.2.3#72005)