Our apps have been migrated from Pega 5.5 to 7.1.8.
One of the pega (7.1.8) app servers is configured to take SOAP requests from the front end, there are many PEGA0011 alerts (with response times going to 50+ seconds sometimes), this alert just gives the information about the Service that took more time to respond and no other details.
We couldn't see any other alerts (no database alerts, no external connection alerts..) that we could use to find the reason for the slow response time of the service hosted in pega.
Can someone provide suggestions on how to analyse further in this case?
Do you know the rate of incoming SERVICE calls being made ? I mean : how many requests per minute ?
What are the settings for your Requestor Pool ? I'm not sure: whether the PEGA0011 include or exclude 'waiting time' here or not: but assuming for the moment that they do: perhaps your incoming requests are spending time waiting for a free Requestor to be made available in the Pool ?
You can use SMA to monitor the Requestor Pools: to see if this is a possiblity - you can also check your logs for any evidence of any explicit timeouts ('Timed Out Waiting for Requestor' I think the message is).
I would NOT just increase your Requestor Pool setting without first monitoring them - because you have to consider the trade-off between time waiting and resources (memory mostly) used.
Posted: 6 years ago
Posted: 9 Feb 2016 10:46 EST
Domenico Giffone (DomenicoGiffone)
Senior Principal Software Engineer