[
https://issues.jboss.org/browse/WFLY-2403?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on WFLY-2403:
-----------------------------------------------
Martin Simka <msimka(a)redhat.com> made a comment on [bug
970679|https://bugzilla.redhat.com/show_bug.cgi?id=970679]
By following steps to reproduce I got:
[standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --enabled=true
--jndi-name=java:jboss/datasources/Test2
--connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1
[standalone@localhost:9999 /] data-source disable --name=Test2
operation-requires-reload true
process-state reload-required
[standalone@localhost:9999 /] re
read-attribute read-operation reload
[standalone@localhost:9999 /] reload
[standalone@localhost:9999 /]
/subsystem=datasources/data-source=Test2:read-attribute(name=enabled)
{
"outcome" => "success",
"result" => false
}
[standalone@localhost:9999 /]
but there is another problem:
[standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --enabled=true
--jndi-name=java:jboss/datasources/Test2
--connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1
[standalone@localhost:9999 /]
/subsystem=datasources/data-source=Test2:read-attribute(name=enabled)
{
"outcome" => "success",
"result" => false
}
datasource is not enabled, it requires restart/reload, but it doesn't notifies user.
[standalone@localhost:9999 /] reload
[standalone@localhost:9999 /]
/subsystem=datasources/data-source=Test2:read-attribute(name=enabled)
{
"outcome" => "success",
"result" => true
}
Is it part of this issue or is it another issue? Should I create new BZ?
Cannot disable Datasource or XADatasource in standalone and domain
modes
------------------------------------------------------------------------
Key: WFLY-2403
URL:
https://issues.jboss.org/browse/WFLY-2403
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Stefano Maestri
Assignee: Stefano Maestri
Description of problem:
Cannot disable a Datasource or XADatasource in standalone mode. It's back to enabled
state after server reload.
Version-Release number of selected component (if applicable):
6.1
How reproducible:
Always
Steps to Reproduce:
Use the http management interface or the CLI
1.Create a Datasource of XADatasource
2.Disable it
3.The response indicates a server reload is required
4.Execute the reload operation
Actual results:
The datasource is back to enabled state
Expected results:
The datasource should be in disabled state
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira