You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the EDC Discovery Service, it is currently possible to register multiple EDC connectors with the same URL for the same BPNL. This leads to incorrect behavior in business apps. E.g. as notification messages are repeatedly sent to the same EDC URL which causes incorrect states.
Current Behavior
The system allows the registration of multiple EDC connectors with the identical URL for the same BPNL.
As a result, notifications are repeatedly sent to the same URL.
Expected Behavior
The EDC discovery service should not allow multiple registrations of the same URL for a single BPNL. Alternatively, the API should detect and filter out redundant URLs to prevent incorrect processing.
Steps To Reproduce
Register multiple EDC connectors with the same URL for the same BPNL in the EDC Discovery Service.
Trigger the Trace-X notification process.
Observe that notifications are repeatedly sent to the same URL.
Impact:
Redundant notifications create unnecessary overhead and disrupt the Trace-X notification process.
This may lead to inconsistencies, performance issues, or unintended behavior.
Suggested Solutions:
Implement a validation mechanism to prevent the registration of multiple connectors with the same URL for a single BPNL.
Enhance the API to detect and filter duplicate URLs.
The text was updated successfully, but these errors were encountered:
In the EDC Discovery Service, it is currently possible to register multiple EDC connectors with the same URL for the same BPNL. This leads to incorrect behavior in business apps. E.g. as notification messages are repeatedly sent to the same EDC URL which causes incorrect states.
Current Behavior
The system allows the registration of multiple EDC connectors with the identical URL for the same BPNL.
As a result, notifications are repeatedly sent to the same URL.
Expected Behavior
The EDC discovery service should not allow multiple registrations of the same URL for a single BPNL. Alternatively, the API should detect and filter out redundant URLs to prevent incorrect processing.
Steps To Reproduce
Register multiple EDC connectors with the same URL for the same BPNL in the EDC Discovery Service.
Trigger the Trace-X notification process.
Observe that notifications are repeatedly sent to the same URL.
Impact:
Redundant notifications create unnecessary overhead and disrupt the Trace-X notification process.
This may lead to inconsistencies, performance issues, or unintended behavior.
Suggested Solutions:
Implement a validation mechanism to prevent the registration of multiple connectors with the same URL for a single BPNL.
Enhance the API to detect and filter duplicate URLs.
The text was updated successfully, but these errors were encountered: