Support Article

Requestors not returning to Requestors Pools

SA-33925

Summary



The users system has agents / listeners that are configured to access a file server path.

Every time if the connection towards the file server path is lost, the Requestor is unable to return to the Requestors Pools and would remain in active status.
And since their Service Package Pooling is configured to have only a maximum of 10 active Requestors. Once it reaches the maximum active Requestors, the system would give user to perform a manual intervention by clearing the Requestors Pools manually.

The user is looking for help to advise us on how can they place the Requestors back to the Requestors Pools programmatically.


Error Messages



Not Applicable


Steps to Reproduce



Manually insert a file to be processed in the file server path, while the agents / listeners wakes up to process, rename the file server path to force the connection to stop. This will cause the Requestors to remain in active status


Root Cause



Not Applicable

Resolution



Java Step:
com.pega.pegarules.priv.management.MBeanManagement.executeMBeanOperation(aMBeanName, aOperationName, aParam1, aParam2, aParam3);

Parameters:
aMBeanName (MBean Name)has to be "com.pega.pegarules.management.RequestorPools"
aOperationName(Operation Name) should be "Clear".
aParam1 has to be the service package name.
aParam2 and aParam3 can be null



Published February 20, 2017 - Updated February 21, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.