[XMLRPC-177] maxThreads independent from worker pool size

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.3
• Component/s: Source
• Environment: all
• Assignee: Unassigned
• Reporter: Timo Boehme
• Created: 02/Oct/09 13:38
• Updated: 02/Oct/09 13:38

Description

The number of concurrent XmlRpcWorkers is controlled by XmlRpcController.getMaxThreads(). The same property is used to control pool size for XmlRpcWorker (in XmlRpcWorkerFactory). There are two deficiencies of using only this single property. First if I don't specify a maximum number of worker threads (default) no pooling takes place. Second it is common practice to keep a small pool of threads (sufficient for 90% of time) but allow more concurrent threads in peak periods. Thus I would propose to add another property getMaxPoolSize() to XmlRpcController which is used to control pool size (for backward compatibility setMaxThreads() could also change maxPoolSize in case this property is 0).