Red Hat Bugzilla – Bug 1019262
Datasource is not removed from EAP 5 server till its restart
Last modified: 2014-09-22 06:10:19 EDT
Description of problem:
In order to really remove datasource it is necessary to restart EAP 5 server but user of JON is not informed about it.
This is regression to the behavior of JON 3.1.2 where datasource was removed from the server without need of restart
Version-Release number of selected component (if applicable):
JON 3.2.0.ER3 vs EAP 5.2.0
How reproducible: always
Steps to Reproduce:
1. import EAP5 to JON server
2. create for example XA Datasource named testXADS
3. look to EAP 5 jmx console to jboss.jdbc:datasource=testXADS,service=metadata
4. remove created XA Datasource via JON
5. see via jmx console that the datasource is unchanged in EAP 5
- after you reboot EAP 5 server the datasource is finally removed
datasource is not removed from EAP 5 server before actual restart of the server and at the same time user is not informed about it
datasource should be removed without any need of restart
The same goes for Queues and Topics
Moving to unspecified target milestone as only JON 3.2.0 'blockers'(https://url.corp.redhat.com/bz-jon32-blockers-list-notmodified-nodocs) will make it into subsequent builds after ER5.
Are we sure this a regression from 3.1.2 or was it a change from the behavior of managing EAP4 instances?
Yes, we are sure that with JON 3.1.2 user didn't have to restart the server. It definitely isn't caused by change in EAP 5 (before it was also tested with EAP 5.2)
OK, we will try and fit this into 3.3.0, assigning to Thomas for further evaluation.
This is not a bug in the EAP5 plugin.
The datasource ManagedComponent is correctly removed and the parent deployment as well (leading to removal of the xxx-ds.xml file). It's just a JMX Bean which is left behind, and the EAP5 plugin has no control on it.
Creating a datasource with the same JNDI name after removal works.
The profile service should remove the JMX Bean. Consider opening a BZ against EAP5.