Bug 1019262
Summary: | Datasource is not removed from EAP 5 server till its restart | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Radim Hatlapatka <rhatlapa> |
Component: | Plugin -- JBoss EAP 5 | Assignee: | Thomas Segismont <tsegismo> |
Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | JON 3.2 | CC: | jshaughn, myarboro, rhatlapa |
Target Milestone: | ER04 | ||
Target Release: | JON 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-22 10:10:19 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Radim Hatlapatka
2013-10-15 11:32:04 UTC
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. |