In previous versions of JBoss EAP 6, it was found that the root domain resource from the domain controller was not getting applied to the slave host controllers. Instead the slave host controllers would use their own root resource.
This meant that when connecting to the slave domain controller directly, the version numbers in the root domain resource was the version of the slave domain controller, so the domain configuration was not homogeneous across the controllers in the domain.
In this release of the product, the slave registration process was updated to apply the root domain resource and the version numbers are now the same across the whole domain.
It currently does not apply the root resource values, meaning a 6.2.0 slave and on the 6.x branch so far will use its local versions in the root resource, so the domain model is not in sync. e.g.
onnect directly to to 6.1.1 slave - gets domain version from master
[domain@localhost:19999 /] :read-resource
{
"outcome" => "success",
"result" => {
"deployment" => undefined,
"deployment-overlay" => undefined,
"management-major-version" => 1,
"management-micro-version" => 0,
"management-minor-version" => 6,
"name" => "Unnamed Domain",
"namespaces" => [],
"path" => undefined,
"product-name" => "EAP",
"product-version" => "6.3.0.Alpha3",
"profile" => undefined,
"release-codename" => "Janus",
"release-version" => "7.4.0.Final-redhat-SNAPSHOT",
Connect directly to 6.2.0 slave - does not get domain version from master
[domain@localhost:19999 /] :read-resource
{
"outcome" => "success",
"result" => {
"management-major-version" => 1,
"management-micro-version" => 0,
"management-minor-version" => 5,
"name" => "Unnamed Domain",
"namespaces" => [],
"product-name" => "EAP",
"product-version" => "6.2.0.GA",
"release-codename" => "Janus",
"release-version" => "7.3.0.Final-redhat-14",
The 6.2.0 slave should look the same as the 6.1.1 slave for these attributes. I noticed this while setting up mixed domain testing against 6.2.0 slaves.
It currently does not apply the root resource values, meaning a 6.2.0 slave and on the 6.x branch so far will use its local versions in the root resource, so the domain model is not in sync. e.g. onnect directly to to 6.1.1 slave - gets domain version from master [domain@localhost:19999 /] :read-resource { "outcome" => "success", "result" => { "deployment" => undefined, "deployment-overlay" => undefined, "management-major-version" => 1, "management-micro-version" => 0, "management-minor-version" => 6, "name" => "Unnamed Domain", "namespaces" => [], "path" => undefined, "product-name" => "EAP", "product-version" => "6.3.0.Alpha3", "profile" => undefined, "release-codename" => "Janus", "release-version" => "7.4.0.Final-redhat-SNAPSHOT", Connect directly to 6.2.0 slave - does not get domain version from master [domain@localhost:19999 /] :read-resource { "outcome" => "success", "result" => { "management-major-version" => 1, "management-micro-version" => 0, "management-minor-version" => 5, "name" => "Unnamed Domain", "namespaces" => [], "product-name" => "EAP", "product-version" => "6.2.0.GA", "release-codename" => "Janus", "release-version" => "7.3.0.Final-redhat-14", The 6.2.0 slave should look the same as the 6.1.1 slave for these attributes. I noticed this while setting up mixed domain testing against 6.2.0 slaves.