IllegalStateException, StartException, JBAS010433, JBAS010432 when enabling newly created datasource in the Admin Console in EAP 6

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6
  • All data source types

Issue

  • Attempting to disable, change and re-enable a datasource created in the web based admin console
  • Re-enable fails and the server.log reports the following failure
... ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-16) Error during the deployment of java:jboss/datasources/MyNewDS: java.lang.IllegalStateException
        at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
        at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.getTransactionIntegration(AbstractDataSourceService.java:411)
        at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:517)
        ...

... ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC000001: Failed to start service jboss.data-source.java:jboss/datasources/MyNewDS: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/MyNewDS: JBAS010433: Error during the deployment of MyNewDS
        at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:127)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
        ...
Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf
        at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:122)
        ...

Resolution

This is a known issue in releases prior to EAP 6.4.0. One of the following may be used to resolve the issue in earlier releases

  • Disable the datasource, make desired changes to configuration, restart the application server and re-enable the datasource
  • Create datasources using the CLI console

Re-enable succeeds in EAP 6.4.0 and later, however, the log may still record a failure1

Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.