[jboss-jira] [JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFCORE-2526:
-------------------------------------
    Fix Version/s: 3.0.0.Beta28
                       (was: 3.0.0.Beta27)


> Domain mode passed unwanted sys props to spawned servers
> --------------------------------------------------------
>
>                 Key: WFCORE-2526
>                 URL: https://issues.jboss.org/browse/WFCORE-2526
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>            Reporter: John Mazzitelli
>            Assignee: Brian Stansberry
>            Priority: Critical
>             Fix For: 3.0.0.Beta28
>
>
> 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



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)