[jboss-jira] [JBoss JIRA] Resolved: (AS7-1076) (Xa)DatasourceRemove does not clean up services properly
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Wed Jun 22 01:22:23 EDT 2011
[ https://issues.jboss.org/browse/AS7-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry resolved AS7-1076.
-----------------------------------
Resolution: Done
> (Xa)DatasourceRemove does not clean up services properly
> --------------------------------------------------------
>
> Key: AS7-1076
> URL: https://issues.jboss.org/browse/AS7-1076
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JCA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.0.0.CR1
>
>
> Fails in the CLI as well:
> [standalone at localhost:9999 /] cd subsystem=datasources
> [standalone at localhost:9999 subsystem=datasources] cd data-source=foo
> [standalone at localhost:9999 data-source=foo] :add(name=foo,jndi-name=bar,pool-name=foo_Pool,connection-url=badconnection,driver-name=h2)
> {"outcome" => "success"}
> [standalone at localhost:9999 data-source=foo] cd ..
> [standalone at localhost:9999 subsystem=datasources] :read-children-resources(child-type=data-source)
> {
> "outcome" => "success",
> "result" => {
> "foo" => {
> "background-validation" => undefined,
> "background-validation-minutes" => undefined,
> "blocking-timeout-wait-millis" => undefined,
> "connection-url" => "badconnection",
> "driver-name" => "h2",
> "idle-timeout-minutes" => undefined,
> "jndi-name" => "bar",
> "max-pool-size" => undefined,
> "min-pool-size" => undefined,
> "pool-name" => "foo_Pool",
> "pool-prefill" => undefined,
> "pool-use-strict-min" => undefined,
> "use-fast-fail" => undefined
> },
> "java:/H2DS" => {
> "background-validation" => false,
> "background-validation-minutes" => undefined,
> "blocking-timeout-wait-millis" => undefined,
> "connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1",
> "driver-name" => "h2",
> "enabled" => true,
> "flush-strategy" => "FailingConnectionOnly",
> "idle-timeout-minutes" => undefined,
> "jndi-name" => "java:/H2DS",
> "jta" => true,
> "max-pool-size" => undefined,
> "min-pool-size" => undefined,
> "password" => "sa",
> "pool-name" => "H2DS",
> "pool-prefill" => false,
> "pool-use-strict-min" => false,
> "use-ccm" => true,
> "use-fast-fail" => false,
> "use-java-context" => true,
> "user-name" => "sa",
> "validate-on-match" => false
> }
> }
> }
> [standalone at localhost:9999 subsystem=datasources] cd data-source=foo
> [standalone at localhost:9999 data-source=foo] :remove
> {"outcome" => "success"}
> [standalone at localhost:9999 data-source=foo] :add(name=foo,jndi-name=bar,pool-name=foo_Pool,connection-url=badconnection,driver-name=h2)
> {
> "outcome" => "failed",
> "failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.bar is already registered",
> "rolled-back" => true
> }
> [standalone at localhost:9999 data-source=foo]
> [standalone at localhost:9999 data-source=foo] cd ..
> [standalone at localhost:9999 subsystem=datasources] :read-children-resources(child-type=data-source)
> {
> "outcome" => "success",
> "result" => {"java:/H2DS" => {
> "background-validation" => false,
> "background-validation-minutes" => undefined,
> "blocking-timeout-wait-millis" => undefined,
> "connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1",
> "driver-name" => "h2",
> "enabled" => true,
> "flush-strategy" => "FailingConnectionOnly",
> "idle-timeout-minutes" => undefined,
> "jndi-name" => "java:/H2DS",
> "jta" => true,
> "max-pool-size" => undefined,
> "min-pool-size" => undefined,
> "password" => "sa",
> "pool-name" => "H2DS",
> "pool-prefill" => false,
> "pool-use-strict-min" => false,
> "use-ccm" => true,
> "use-fast-fail" => false,
> "use-java-context" => true,
> "user-name" => "sa",
> "validate-on-match" => false
> }}
> }
> Bug appears to be use of the wrong name for the service names in AbstractDatasourceRemove. Should be the JNDI name to match the add handler.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list