Workaround: Workaround Exists
Workaround Description: disable and enable the datasource using CLI, after that it will start working in console as well. Another workaround is to force server reload. 
project_key: JBPAPP6

Create a (xa)datasource in admin console. Try to disable it using the appropriate button. This error will happen:

{noformat}
Request
{
    "xa-datasource-class" => "org.h2.jdbcx.JdbcDataSource",
    "pad-xid" => false,
    "wrap-xa-resource" => false,
    "same-rm-override" => false,
    "interleaving" => false,
    "name" => "qrh",
    "driver-name" => "h2",
    "password" => "",
    "enabled" => true,
    "user-name" => "",
    "security-domain" => "",
    "jndi-name" => "java:/uyyyy",
    "pool-name" => "",
    "transaction-isolation" => "",
    "new-connection-sql" => "",
    "connection-url" => "",
    "driver-class" => "",
    "valid-connection-checker-class-name" => "",
    "check-valid-connection-sql" => "",
    "background-validation" => false,
    "background-validation-millis" => -1L,
    "validate-on-match" => false,
    "stale-connection-checker-class-name" => "",
    "exception-sorter-class-name" => "",
    "prepared-statements-cache-size" => -1L,
    "share-prepared-statements" => false,
    "use-ccm" => false,
    "operation" => "disable",
    "address" => [
        ("subsystem" => "datasources"),
        ("xa-data-source" => "qrh")
    ],
    "operation-headers" => {"allow-resource-service-restart" => true}
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "failure-description" => "JBAS010455: Data-source service [qrh] is not enabled",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "restart-required"}
}
{noformat}

It states that "Data-source service [qrh] is not enabled" even though the datasource has property "enabled" equal "true". 
After you disable the datasource in CLI using :disable operation (this works) and then enable it back -> from this point, disabling and enabling in console will work, just the first time (after creation) it doesn't.

*RESOLUTION* - the datasource has its property "enabled" wrongly set to true, even though it is actually disabled after creation. This is a JCA subsystem issue.