Skip to main content

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

Configuring the Java thread pool

Updated on June 4, 2021

The computer telephony integration (CTI) link engine runs as a set of Java objects on the application server. To reduce latency and improve the system performance, you can configure the number of Java threads that each CTI link uses.

A Java thread pool is a pool of threads that process events or manage notifications from the CTI server. You can specify the maximum and minimum number of threads that a link uses. The number of threads required varies depending on the environment. However, for most environments, a Java thread can process events for up to 20 operators. If your deployment has many users on a node using the same CTI link, ensure that the maximum threads and users per thread values are adequate to handle requests from your CTI server.
  1. In the header of Dev Studio, click ConfigureChannel ServicesPega CallAdministration and Configuration.
  2. On the CTI Links tab, in the Actions list in the row of the CTI link for which you want to edit the Java thread pool size, click Edit.
  3. On the Advanced tab, in the Engine Threads section, configure the threads:
    1. In the Minimum Threads field, enter the minimum number of threads that the CTI link uses.
    2. In the Maximum Threads field, enter the maximum number of threads that the CTI link uses.
    3. In the Users per Thread field, enter the maximum number of operators for which you want each Java thread to process events. When this threshold is met, a new thread is created.
  4. Confirm your updates by clicking Save.
Result: Your changes take effect the next time you restart the CTI link.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us