[
https://issues.jboss.org/browse/WFCORE-1703?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-1703:
-------------------------------------
Summary: JVM resource handling of jvm-options should detect -D options and integrate
with system-property logic (was: It is not possible to set jboss.modules.system.pkgs per
server in domain mode)
JVM resource handling of jvm-options should detect -D options and
integrate with system-property logic
------------------------------------------------------------------------------------------------------
Key: WFCORE-1703
URL:
https://issues.jboss.org/browse/WFCORE-1703
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.2.0.Final
Reporter: Bogdan Ilchyshyn
Priority: Minor
It is not possible to set {{jboss.modules.system.pkgs}} property per server / server
group in domain configuration. Even when the following configuration is added to
{{host.xml}}:
{code:xml}
<server name="server-one" group="main-server-group">
<jvm name="default">
<jvm-options>
<option value="-Djboss.modules.system.pkgs=my.package"/>
...
{code}
It is overridden by configuration in {{domain.conf}}:
{noformat}
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS
-Djava.awt.headless=true"
{noformat}
This is an issue for configuring third-party java agents per-server. A problem described
in WFLY-895 adds to this. One should either add a whole bunch of things to _all_ jvms in
domain in order to make agent work, or remove config from {{domain.conf}} to avoid
overrides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)