Question

16
Replies
2601
Views
Fran Collins (COLLF-1)
PEGA
Director, Consulting
Pegasystems Inc.
JP
COLLF-1 Member since 2012 21 posts
PEGA
Posted: July 21, 2017
Last activity: August 3, 2017
Posted: 21 Jul 2017 3:14 EDT
Last activity: 3 Aug 2017 4:09 EDT
Closed
Solved

[PEGA 7.1.6] Connect-SOAP Response Timeout

Hello,

We have set our Connect-SOAP Response Timeout to 120 seconds.

In Production we had an Long-Running Connect SOAP Alert for the same Connect-SOAP rule. It was 231 seconds.

We investigated the Connect-SOAP in DEV, and had the following two behaviors:

1.) If endpoint was available, but took over 120 seconds to response, the Response Timeout properly triggered.

2.) If the endpoint was unavailable, we received an immediate response, and the resources were properly released.

What could have made our Production scenario different than the DEV scenario? Why did it hang in Production for such a long time?

I would greatly appreciate any insight you can provide on this matter.

Thank you!

Fran

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.