[ https://issues.jboss.org/browse/WFCORE-350?page=com.atlassian.jira.plugin... ] Brian Stansberry edited comment on WFCORE-350 at 1/26/18 8:04 PM: ------------------------------------------------------------------ The intent is if you set them on the HC or PC process they have no meaningful effect, i.e. the HC/PC doesn't use them itself and doesn't pass them to its servers. An HC can control > 1 server so setting server specific settings to a common value on the HC and then having that passed in to its servers means all the servers will collide. In your example you'd have multiple processes fighting over /var/logs/wildfly/server.log. You use the /host=x/server-config=y/system-property=z resources if you want control these properties on the servers. I'm not sure but I believe you can use domain-wide, host-wide or server-group wide system-property resources for jboss.server.... props if you want, but you need to understand what processes are going to get those properties and avoid collisions. was (Author: brian.stansberry): The intent is if you set them on the HC or PC process they have no meaningful effect, i.e. the HC/PC doesn't use them itself and doesn't pass them to its servers. An HC can control > 1 server so setting server specific settings to a common value on the HC and then having that passed in to its server means all the servers will collide. In your example you'd have multiple processes fighting over /var/logs/wildfly/server.log. You use the /host=x/server-config=y/system-property=z resources if you want control these properties on the servers. I'm not sure but I believe you can use domain-wide, host-wide or server-group wide system-property resources for jboss.server.... props if you want, but you need to understand what processes are going to get those properties and avoid collisions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)