[jboss-jira] [JBoss JIRA] (WFCORE-2091) Mixed domain with EAP 6 slaves: data sources operations broken
Lin Gao (JIRA)
issues at jboss.org
Wed Dec 7 10:06:00 EST 2016
[ https://issues.jboss.org/browse/WFCORE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Gao moved JBEAP-7739 to WFCORE-2091:
----------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2091 (was: JBEAP-7739)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
(was: JCA)
Affects Version/s: (was: 7.1.0.DR9)
> Mixed domain with EAP 6 slaves: data sources operations broken
> --------------------------------------------------------------
>
> Key: WFCORE-2091
> URL: https://issues.jboss.org/browse/WFCORE-2091
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Blocker
>
> 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:
> {noformat}
> [domain at 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]
> }
> {noformat}
> The fix for JBEAP-5770 seems to be the cause.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list