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 using HTTP call and call response scenario we allow 2 sources with http.status.code = 200 and [2|4]00 to register in Siddhi app. However, when the response arrives, according to our current logic in findAndGetResponseSource method we randomly pick a source from the map matching the regex and send a response. Please find a sample app to simulate this below.
#156 This attempted to fix the issue but further effort is needed to clone Carbon http messages between sources.
wso2/product-sp#1051 is a related issue arising from the inconsistency of equals function in ResponseSourceId.java with regard to registering the source and removing it during shutting down.
When using HTTP call and call response scenario we allow 2 sources with http.status.code = 200 and [2|4]00 to register in Siddhi app. However, when the response arrives, according to our current logic in
findAndGetResponseSource
method we randomly pick a source from the map matching the regex and send a response. Please find a sample app to simulate this below.We need to have a robust mechanism to handle such responses which need to be sent to multiple sources
The text was updated successfully, but these errors were encountered: