Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Must clear requestor pool after changing RuleSet lists of services

Updated on November 15, 2015

Summary

A developer asks:

I have a JMS service which belongs to the XactwareJMS service package.  The XactwareJMS service packages uses access group named MyXactwareService.  MyXactwareService relies only on the application MyXactWare.

In MyXactware, I change the version of some of the RuleSets in the Application RuleSets list.  Then I run a test, but it appears that the rules added to the access group do not take effect. 

If then I delete the requestor pool, and the new rules do take affect.  Why is it necessary to delete the requestor pool?



 

Suggested Approach

Once a requestor is in the pool, its application and RuleSet list is determined will not change. Any new requestors added to the pool would pick up the new RuleSets.

To avoid a mix of requestors in the pool after you modify the access group, use the Monitor servlet to clear the requestor pool.

 

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us