[
https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-2035 at 6/27/13 9:01 AM:
--------------------------------------------------------------
also what we have found out is if the server is recycled after the remove, then it works
fine. It looks like when remove operation is done AS does not completely remove the
services based on the previous ones, and trying to create the new services based on same
names gets into creation issues.
I did not see the workaround text before, possibly we can implement that in the Admin api,
not sure if that works
was (Author: rareddy):
also what we have found out is if the server is recycled after the remove, then it
works fine. It looks like when remove operation is done AS does not completely remove the
services based on the previous ones, and trying to create the new services based on same
names gets into creation issues.
DeleteDataSource method on Admin API does not completely delete the
Connection Factory
--------------------------------------------------------------------------------------
Key: TEIID-2035
URL:
https://issues.jboss.org/browse/TEIID-2035
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
ConnectionFactory requires a two step creation process
1) create the resource-adaptor section
2) connection factory section
The delete is removing the (2) and not (1). Thus any subsequent creates using the same
name fails.
--
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