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
When the wsa:RelatesTo header is unspecified in the response of the WS-enabled service, the messageID should be used in MI to correlate the backend response with the request. But currently, the MessageID of the response is recognized as the wsa:RelatesTo instead of the actual MessageID.
The message flow will fail with the following error.
TS: [] TID: [] [2024-03-20 09:50:58,614] WARN {SynapseCallbackReceiver} - Synapse received a response for the request with message Id : http://www.w3.org/2005/08/addressing/unspecified and correlation_id : xxx But a callback is not registered (anymore) to process this response
The text was updated successfully, but these errors were encountered:
When the wsa:RelatesTo header is unspecified in the response of the WS-enabled service, the messageID should be used in MI to correlate the backend response with the request. But currently, the MessageID of the response is recognized as the wsa:RelatesTo instead of the actual MessageID.
Steps to reproduce:
Create a WS-enabled proxy service where the backend of this proxy service returns the wsa:RelatesTo header as http://schemas.xmlsoap.org/ws/2004/08/addressing/id/unspecified.
The message flow will fail with the following error.
TS: [] TID: [] [2024-03-20 09:50:58,614] WARN {SynapseCallbackReceiver} - Synapse received a response for the request with message Id : http://www.w3.org/2005/08/addressing/unspecified and correlation_id : xxx But a callback is not registered (anymore) to process this response
The text was updated successfully, but these errors were encountered: