Affects: Compatibility/Configuration, Release Notes Help Desk Ticket Reference: https://na7.salesforce.com/500A0000009gBmZ Steps to Reproduce: - Start the application server - Deploy a datasource or use the existing datasource - Disable the given datasource - Verify the preferred datasource has been disabled via admin console - Try to enable the datasource via CLI - The "JBAS014749: Operation handler failed: Service jboss.data-source-config.ExampleDS is already registered" will be thrown project_key: JBPAPP6 It's not possible to enable a datasource via CLI. The following exception gets thrown : JBAS014749: Operation handler failed: Service jboss.data-source-config.ExampleDS is already registered
Fixed in CR1
I don't understand why this was "rejected" and has a comment "Fixed in CR1" ? We just ran into this issue with JBoss EAP 6.0.0 GA, and the issue is clearly still there. Reproduction: - add a jdbc driver via a module - edit standalone.xml, adding a driver and a datasource. <driver name="mysql" module="com.mysql.jdbc"> <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class> </driver> <datasource jndi-name="java:/mysqlDS" pool-name="mysqlDS"> <connection-url>jdbc:mysql://localhost:3306/db</connection-url> <driver>mysql</driver> <security> <user-name>user</user-name> <password>pass</password> </security> <validation> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> </validation> </datasource> Note that the datasource does not have the "enabled" attribute. - start the server - in the GUI, use the "enable" button => fails - in the CLI: /subsystem=datasources/data-source=mysqlDS:read-attribute(name=enabled) -> reports "false" write-attribute does not work. Next, stop and edit the xml so it reads: <datasource jndi-name="java:/mysqlDS" pool-name="mysqlDS" enabled="false"> - start, and access the "enable" button in the GUI -> it now WORKS. Disabling also works. - CLI: nothing changed, you still cannot write to the attribute. read-resource-description shows why: it's read-only. So in summary: - attribute not present -> GUI cannot toggle it - attribute present -> GUI works fine - both cases, CLI cannot write the attribute.
Link: Added: This issue Cloned to JBPAPP-9452
I've checked. There is a problem in xml parser default value for this attribute. I'm fixing it. There is also a misuse of attribute/operation in cli here: command line tool works fine using proper commands :enable and :disable. BTW in description enabled attribute is declared read-only and works as expected.
Link: Added: This issue Cloned to JBPAPP-9453
Verified on EAP 6.0.1 ER2
Release Notes Docs Status: Added: Not Yet Documented Affects: Removed: Compatibility/Configuration Added: Compatibility/Configuration,Release Notes
Updated release note fields.
reopening for release note updates
Writer: Added: sgilda
Writer: Removed: sgilda Added: tomwells
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: Datasources could not be enabled via the Management CLI, due to an XML parser error in the default value of the enabled attribute. The error has been corrected, and datasources can now be enabled successfully.
Release Notes Docs Status: Removed: Documented as Resolved Issue Writer: Removed: tomwells Release Notes Text: Removed: Datasources could not be enabled via the Management CLI, due to an XML parser error in the default value of the enabled attribute. The error has been corrected, and datasources can now be enabled successfully. Docs QE Status: Removed: NEW