Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 885617

Summary: Unable to create datasource with name it was created earlier but deleted
Product: [JBoss] JBoss Operations Network Reporter: Jakub Cechacek <jcechace>
Component: Plugin -- JBoss EAP 5Assignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: jkudrnac, myarboro, tsegismo
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-12 19:49:42 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 Jakub Cechacek 2012-12-10 08:57:41 UTC 
I am not able to create new Datasource in EAP5 server if it uses the same name as Datasource which existed before but was already deleted.

The cause of this behaviour is that *.xml file remains in deployment directory of EAP instance even though JON and jmx no longer knows about it.



Steps to reproduce:

1 - create through JON ui new Datasource (ds type doesn't matter in this scenario) for EAP5.
2 - After successful creation delete it. 
3 - try to create new datasource of the same name. It will fail with exception complaining about existence of *.xml file. 


This is the same behaviour as described in 885136
Comment 2 Thomas Segismont 2013-06-12 19:49:42 UTC 

*** This bug has been marked as a duplicate of bug 885136 ***