[jboss-jira] [JBoss JIRA] (WFCORE-3830) JAVA_OPTS is not passed to DC and HC JVMs in domain.ps1

[ https://issues.jboss.org/browse/WFCORE-3830?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3830: ------------------------------------------ N.B. The term DC is not meaningful in this context. A Host Controller is a kind of java process that exists in a WildFly managed domain. The term Domain Controller is used for an HC that has a few particular settings in its xml config that cause it to perform a particular role as the master controlling other slave HCs. But it's still an HC process. The scripts have nothing to do with whether a particular HC is a master or a slave. In discussions of scripts they are all HCs. There's another process type in a managed domain that is relevant to the scripts -- the Process Controller. The PC is the java process that is actually started by the scripts. The PC is actually the one that spawns the HC process, not the scripts. (The PC also spawns the 3rd type of managed domain process, the actual appserver processes.) Part of what you can to in the various .conf files is manipulate PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS, which allow you to have separate control over opts passed by the script directly to the PC JVM it launches vs those passed as strings to the PC and used by it internally when it launches the HC. The default value for both PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS is whatever the value of JAVA_OPTS is. (The primary reason we have PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS is to allow debugging to be turned on separately for the PC or HC.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)