wso2
Replay transaction solution for write operations
Description
There is a requirement to capture the request details that are coming to the GW level so that they can replay those if they identify a transaction failure. By default, if we want to capture the request details(headers and the payload) from the GW level and send it to a separate destination, we need to use the clone mediator, and it will build the message. But with the load and message sizes, it will impact the performance of the server.
We need to consider below details when implementing the feature.
- queue size should be configurable
- identify the unique identifier and delimeter which should be appended to the message chunks.
- If there is a queue overflow, it should drop the messages without affecting to the primary backend call. There should be comprehensive logs to see that and identify the reason, etc.
- This should be configurable for API level and then resource level.
Affected Component
APIM
Version
4.3.0
Hi Team, A gentle reminder on the below ETA
ETA information for the fix will be as follows.
Product: wso2am 4.3.0 full Public git issue: https://github.com/wso2/api-manager/issues/4421 Best Case Estimate: 2025-10-23 Most Likely Estimate: 2025-10-30 Worst Case Estimate: 2025-11-13 Thanks and Regards Upahara
