after performing Stop Requestor for long running requests, the system is hanging. I'm not able to perform a Clear Requestor Pool from SMA, SMA reacts not for the click. Sometimes the next requests aren't executed. The client gets never an answer from Pega, the request is terminated after the configured time-out of the Soap Client. For those requests I can't see any message in the log.
Is it possible to perform an Activity or another rule, when a request gets a Stop?
sorry. But your suggestion is absolute NOT helpfull.
Is there a safe way to terminate a request WITHOUT producing problems in Pega? Is there no way to get a signal inside the running code that the requestor should be terminated, to perform a proper clean-up or to configure a time-out for SOAP/REST/HTTP-Services?
Posted: 4 years ago
Posted: 16 Feb 2017 10:01 EST
Gopi Ganapathy (GopiGanapathy)
Principal Software Solutions Engineer
Thanks Gopi for replying and suggesting that this should be an enhancement request. I have gone ahead and submitted this on Uwe's behalf and updated his original post with the Feedback ID. Uwe, please take that Feedback ID to your Account Executive who will assist you moving forward with it.