Running Business Processes and Composite Applications 10.5 | Running Business Processes and Composite Applications | Administering My webMethods Server | My webMethods Server Clustering | Configuring the Number of Purge Threads for a Cluster
 
Configuring the Number of Purge Threads for a Cluster
When a user deletes an item, My webMethods Server marks the item for deletion. The item remains in the system until My webMethods Server purges all pending items, according to a pre-configured schedule, or as a result of a manual trigger of the content purge by a system administrator.
When a purge operation runs in a My webMethods Server cluster, all cluster nodes that have the autodeploy role attempt to purge the pending items. If a large number of items is marked for deletion, the purge operation might execute for a significant amount of time. You can configure the number of threads that remove deleted items form the system and speed up the purge operation using the purge.schedule.maxthreads additional JVM property. The default value of the property is 10.
* To configure the number of purge executor threads
1. Open the custom_wrapper.conf file in a text editor.
2. In the custom_wrapper.conf, file, add the following additional JVM property:
purge.schedule.maxthreads=number_of_threads
3. Save the file and restart My webMethods Server.
For more information about working with the custom_wrapper.conf file, see Configuring JVM Settings for My webMethods Server.

Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.