Details
-
Enhancement
-
Resolution: Done
-
Critical
-
None
-
None
Description
This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props.
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).
See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html