[jboss-jira] [JBoss JIRA] (WFCORE-1052) Add server-config parameter to :reload op
[
https://issues.jboss.org/browse/WFCORE-1052?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1052:
------------------------------------------
Note that this behavior is problematic for the domain config in the context of an HA DC
feature (WFCORE-338). It adds another path via which the domain-wide config can be changed
underneath the cluster of HCs that are attempting to ensure that the domain is using the
correct config.
Add server-config parameter to :reload op
-----------------------------------------
Key: WFCORE-1052
URL: https://issues.jboss.org/browse/WFCORE-1052
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Fix For: 3.0.0.Alpha1
{code}
[13:48] Kabir Khan: @BrianStansberry @JasonGreene
$./build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/bin/standalone.sh
--server-config=20151013-134726769standalone.xml
looks for that file in the snapshots directory
[13:48] Kabir Khan:
[standalone@localhost:9990 /] :list-snapshots
{
"outcome" => "success",
"result" => {
"directory" =>
"/Users/kabir/sourcecontrol/wildfly/git/wildfly-core/build/target/wildfly-core-2.0.0.CR7-SNAPSHOT/standalone/configuration/standalone_xml_history/snapshot",
"names" => [
"20151013-134523280standalone.xml",
"20151013-134726769standalone.xml"
]
}
}
Show less
[13:50] Kabir Khan: server-config should probably be a parameter to the :reload
operation
{code}
Similarly we should add host-config and domain-config parameters to the host's reload
operation. Using domain-config on a non-DC host should fail.
For a domain server, we should not have the server-config parameter.
We should check the existence of the file before the reload actually is done, or we will
end up in a sticky situation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)