[MNT-20165] REST API endpoint lookup failing in APS after recreating an endpoint with identical name Created: 12-Nov-18 Updated: 16-Mar-20 Resolved: 16-Mar-20
|Project:||Service Packs and Hot Fixes|
|Component/s:||APS Identify Manager, APS Kickstart/Studio|
|Type:||Service Pack Request|
|Reporter:||Ciju Joseph [X] (Inactive)||Assignee:||Closed Issues|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
When a REST endpoint in APS is deleted, the entries are not deleted from the DB. Instead they are marked as deleted and the entry is kept in the database. However it is removed from the endpoint UI in APS.
Since a deleted entry is not show in the UI, a user is not aware of the existence of an endpoint with that name! So, if another endpoint is created with the same name, APS processes are returning the exception "javax.persistence.NonUniqueResultException: result returns more than one elements" in the REST call and processes get stuck at the REST call task!
The code where this is failing is EndpointServiceImpl.java -> getConfigurationByName(name)
Steps to reproduce the issue
|Comment by Mark Howarth [ 23-Aug-19 ]|
Reassigning to Doug Gruber, the new PM for APS.
|Comment by Mark Howarth [ 02-Dec-19 ]|
Assigning to Mark Howarth as PM for APS.