We ran a test from Pega in DEV with the same Connector. It timed out, as configured, after 120 seconds, if the response took too long. If the endpoint was unavailable, it immediately returned a response. We have not been able to replicate the scenario in PROD where it did not time out after 120 seconds, but stayed alive until the service returned a response after 231 seconds.
I would expect that, if we ran it from SOAPUI, we would have to wait 231 seconds, as there is no configured timeout in SOAPUI. However, that doesn't really help us understand why Pega's timeout did not trigger. Will it help? Can we set a timeout in SOAPUI? I think the test needs to be done in Pega to determine why Pega's timeout did not trigger. Let me know if I am misunderstanding.
If you have any further guidance, it would be greatly appreciated. We are still not able to make progress on this.
I did not specify in this thread, but this was actually the article I came across during my initial investigation. Unfortunately, it does not shed any light on why we have the behaviour that we do in PROD.
If you have any other information, that would be appreciated.
Thank you for the feedback, but you even stated that turning on enhanced logging for a heavily used interface, which this is, will bog down our logging in PROD, so I won't be able to use this approach. Do you have any other suggestions?
Why would the Connect behaviour be different in DEV and PROD?
My guess is connect rule from pega is not behaving differently in dev or prod. The service provider is behaving differently. They are taking good amount of time to return endpoint failure in prod. And then pega is trying multiple time to connect to the same endpoint resulting the timeout.