Hi Tech Community,
I’m facing the following issue:
A sender using HTTP (which, as we know, is synchronous) sends a payload and expects a response. If the flow crashes, there is no business impact since the sender has a retry mechanism.
The sender side closes the connection after 30 seconds due to business requirements. However, we cannot catch this error because it is not raised during the flow execution but rather occurs outside of it (if I understand correctly how servlets are built). As a result, while the business is not impacted, CPI monitoring detects failures and requires constant checks.
This results in Error 32 - Broken Pipe, as the connection is already closed when the response is attempted to be sent back.
I attempted to implement logic that terminates the flow after 30+ seconds, but the Termination End still sends a response to the sender, causing a failure due to the closed connection.
Does anyone have insights on this issue or ideas on how to prevent sending a response with the HTTP adapter in certain cases?
Looking forward to your responses.
Best regards,
Andrejs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.