[jboss-jira] [JBoss JIRA] Commented: (AS7-1071) Some JNDI names prevent disabling datasources

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610177#comment-12610177 ] 

Brian Stansberry commented on AS7-1071:
---------------------------------------

Should be fixed in new-controllers, although I didn't get a chance to properly validate. If you could validate the fix, I'd appreciate it.

> Some JNDI names prevent disabling datasources
> ---------------------------------------------
>
>                 Key: AS7-1071
>                 URL: https://issues.jboss.org/browse/AS7-1071
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>             Fix For: 7.0.0.CR1
>
>
> It seems that certain JNDI names cause errors:
> 14:25:22,365 WARN  [org.jboss.as.controller] (HttpManagementService-threads - 2) Operation ("disable") failed - address: ([
>     ("subsystem" => "datasources"),
>     ("data-source" => "mysql")
> ]): org.jboss.as.controller.OperationFailedException [ "Data-source service [mysql] is not available" ]
> The datasource in question has a JNDI name with slash:
> [standalone at localhost:9999 /] /subsystem=datasources/data-source=mysql2:read-attribute(name=jndi-name)
> {
>     "outcome" => "success",
>     "result" => "jdbc/mysql2"
> }
> [standalone at localhost:9999 /] /subsystem=datasources/data-source=mysql2:disable                       
> {
>     "outcome" => "failed",
>     "failure-description" => "Data-source service [mysql2] is not available",
>     "rolled-back" => true
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira