[ https://issues.jboss.org/browse/WFLY-6789?page=com.atlassian.jira.plugin.... ] Kylin Soong updated WFLY-6789: ------------------------------ Description: WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute {code} /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]) {code} will throw a exception {code} 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout] {code} If execute without xa-datasource-properties which like previous version {code} /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true) {code} the exception like {code} { "outcome" => "failed", "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource", "rolled-back" => true } {code} To create with xa-data-source add command is a workaround {code} xa-data-source add --name=MariaDBXADS --driver-name=mariadb-xa --jndi-name=java:jboss/datasources/MariaDBXADS --user-name=jdv_user --password=jdv_pass --use-java-context=true --xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost] {code} but most users expect the tree-structure cli and xa-data-source compatible. was: WildFly 10 wants a xa-datasource-properties, but xa-datasource-properties not added as a xa datasources attributes in management resource definition , eg, execute {code} /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true, xa-datasource-properties=[DatabaseName=>products, PortNumber=>3306, ServerName=>localhost]) {code} will throw a exception {code} 'xa-datasource-properties' is not found among the supported properties: [allocation-retry, allocation-retry-wait-millis, allow-multiple-users, background-validation, background-validation-millis, blocking-timeout-wait-millis, capacity-decrementer-class, capacity-decrementer-properties, capacity-incrementer-class, capacity-incrementer-properties, check-valid-connection-sql, connectable, connection-listener-class, connection-listener-property, driver-name, enabled, enlistment-trace, exception-sorter-class-name, exception-sorter-properties, flush-strategy, idle-timeout-minutes, initial-pool-size, interleaving, jndi-name, max-pool-size, mcp, min-pool-size, new-connection-sql, no-recovery, no-tx-separate-pool, pad-xid, password, pool-fair, pool-prefill, pool-use-strict-min, prepared-statements-cache-size, query-timeout, reauth-plugin-class-name, reauth-plugin-properties, recovery-password, recovery-plugin-class-name, recovery-plugin-properties, recovery-security-domain, recovery-username, same-rm-override, security-domain, set-tx-query-timeout, share-prepared-statements, spy, stale-connection-checker-class-name, stale-connection-checker-properties, statistics-enabled, track-statements, tracking, transaction-isolation, url-delimiter, url-property, url-selector-strategy-class-name, use-ccm, use-fast-fail, use-java-context, use-try-lock, user-name, valid-connection-checker-class-name, valid-connection-checker-properties, validate-on-match, wrap-xa-resource, xa-datasource-class, xa-resource-timeout] {code} If execute without xa-datasource-properties which like previous version {code} /subsystem=datasources/xa-data-source=MariaDBXADS:add(driver-name=mariadb-xa, jndi-name=java:jboss/datasources/MariaDBXADS, user-name=jdv_user, password=jdv_pass, use-java-context=true) {code} the exception like {code} { "outcome" => "failed", "failure-description" => "WFLYJCA0069: At least one xa-datasource-property is required for an xa-datasource", "rolled-back" => true } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)