-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR9
-
None
Run a mixed domain where EAP 7.1.0.DR9 is the master and EAP 6.4.0/6.3.0/6.2.0 is a slave server. Operations on data sources are broken due to incompatibility of models:
[domain@127.0.0.100:9990 /] /host=eap640/server=server-one/subsystem=datasources/data-source=ExampleDS:test-connection-in-pool
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0297: Transforming operation {
\"address\" => [
(\"host\" => \"eap640\"),
(\"server\" => \"server-one\"),
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"ExampleDS\")
],
\"operation\" => \"test-connection-in-pool\",
\"operation-headers\" => {
\"caller-type\" => \"user\",
\"access-mechanism\" => \"NATIVE\",
\"domain-uuid\" => \"ae186a65-8c76-41d0-bd23-79154b5f92f7\"
}
} at resource [
(\"host\" => \"eap640\"),
(\"server\" => \"server-one\"),
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"ExampleDS\")
] to subsystem 'datasources' model version '1.3.0' -- attributes [connection-url] WFLYCTL0336: The following attributes are nillable in the current model but must be defined in the target model version: [connection-url]",
"rolled-back" => true,
"result" => [true]
}
The fix for JBEAP-5770 seems to be the cause.
- clones
-
WFLY-7759 Mixed domain with EAP 6 slaves: data sources operations broken
-
- Closed
-
- is caused by
-
JBEAP-5770 connection-url is required even when not used
-
- Verified
-