Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MessageID of the response is recognized as the wsa:RelatesTo instead of the actual MessageID #3330

Closed
karunarathneeshani opened this issue May 13, 2024 · 0 comments · Fixed by wso2/wso2-synapse#2178
Milestone

Comments

@karunarathneeshani
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants