I have an issue where both local AEM instances using the latest SDK, and cloud AEM instances sometimes cannot register themselves as event providers in AIO after redeploy. When I delete all 3 provider registrations (1x localhost + 2x CM) from AIO using its CLI, they can all register correctly. But after some time, they try to reregister, and I can see this error in the event metadata status check as well as in AEM's error.log:
ConflictException:[409 Conflict] during [POST] to [https://api.adobe.io/events/899606/4566206088344857951/4566206088344863396/providers] [ProviderApi#create(String,String,String,ProviderInputModel)]: [{"reason":"Use PUT or PATCH to update: Another provider exists with the same natural key (organization_id, provider_metadata/type, instanceId). Request id: WUNvssICncVHorntw8AnhzVyZ93iCr4P.","message":"187ae187-466a-40d0-a15c-0dd277bfa6fa. Please take a note of the http response `x-request-id` header for debugging/support."}]
Is it a known issue, or perhaps a problem with my configuration? Thanks.
//EDIT:
From other logs i can see that there is issue with parsing conflictId:
The Conflict/409 Error response does not hold a valid conflicting id: `187ae187-466a-40d0-a15c-0dd277bfa6fa. Please take a note of the http response `x-request-id` header for debugging/support.`
Looks like at some point message returned via API was changed from just conflictId to conflictId + message that is breaking integration with AEM.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
The issue has been fixed by changing the aio lib dependency in the AEM project to the newest version (0.1.2 => 1.0.10)
Views
Replies
Total Likes
The issue has been fixed by changing the aio lib dependency in the AEM project to the newest version (0.1.2 => 1.0.10)
Views
Replies
Total Likes