Hi,

How's the requestors pool configured? Did you try unchecking the 'Requires authentication'?

Hi Biagh,

Thanks for the reply, in service package requestore is pool is configured as below,

Max no of idle requestors: 1

Max no of active requestors: 1

Wait time: 10

Tried with and with out authentication, the same is happenning.

Hi,

There is only one requestor in count to accomodate to the pool. Please increase the count of max idle and max active as 5 and 5.

Thanks,

Habeeb Baig

Hi Habeeb,

The mentioned scenario is for testing purposed.

When a new request comes for the first time Pega creates a new requestor (of type APP) and the requestor is moving to idle once the processing is finished. The same be can be observed by “Requestor Pools” in SMA.

Now when a new request comes Pega is creating a new requestor instead of reusing the existing requestor even through its idle.

Hi,

As per the help document, "If an active requestor becomes idle and is returned to the pool when the current number of idle requestors is at this limit, the requestor is deleted."

https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm

Hi Habeeb,

Thanks again, each time when the service is invoked a new requestor is created and is not deleted. i.e after 3 request attempts i can see 3 APP type requestors in SMA (or Remote tracer).

Hi Team,

If any one implemented "stateful" practically, please let me know the details.

Regards,

Satish