Skip to main content


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

Managing queue processors

Updated on July 8, 2022

Use the Admin Studio, Queue processor page to review information about queue processors in your system.

You can trace queue processors and change the state of queue processors. You can also view information about queue processors, such as the node types on which the queue processors run or the number of broken items.

Managing Queue Processor rules requires one of the following privileges:

  • pzQueueProcessorAdministrator
  • pzClusterAdministrator

Viewing the list of queue processors requires the pzQueueProcessorObserver privilege.

Queue Processors for Search and Reporting Service

The system performs indexing of data by using the following Queue Processors: pySASBatchIndexClassesProcessor, pySASBatchIndexProcessor, pySASIncrementalIndexer.

  • Large message exception handling in queue processing

    Queue processing automatically handles large messages that exceed the Stream Service default file size threshold. Pega queue processing uses the Stream Service to queue and delegate processing. Automatic handling prevents oversize messages from breaking.

  • Setting up large message handling for on-premises environments

    Pega Platform queue processing can automatically handle messages that exceed the Stream Service default file size threshold. Setting up this feature prevents large messages from breaking when they generate a RecordTooLargeException exception.

  • Queue processor rules

    A queue processor rule is an internal background process on the server that you can use for queue management and asynchronous processing. You can use standard or dedicated queue processor rules.

  • Queue processor FAQ

    A queue processor rule is an internal background process that you configure for queue management and asynchronous message processing. Use standard queue processor rules for simple queue management or low-throughput scenarios, or use dedicated queue processor rules for higher-scaling throughput, and customized or delayed processing of messages.

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