You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-auto@ws.apache.org by "Timo Boehme (JIRA)" <xm...@ws.apache.org> on 2009/10/02 15:40:23 UTC
[jira] Created: (XMLRPC-177) maxThreads independent from worker
pool size
maxThreads independent from worker pool size
--------------------------------------------
Key: XMLRPC-177
URL: https://issues.apache.org/jira/browse/XMLRPC-177
Project: XML-RPC
Issue Type: Improvement
Components: Source
Affects Versions: 3.1.3
Environment: all
Reporter: Timo Boehme
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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.