[ http://issues.apache.org/jira/browse/AXIS2-761?page=comments#action_12412866 ]
Chuck Williams commented on AXIS2-761: -------------------------------------- My performance bottleneck when hitting the server hard from the client turned out to be the core pool size in SimpleHttpServer's request ThreadPoolExector (SimpleHttpServer.minThreads == 25). The semantics of ThreadPoolExecutor limit the processing threads to this value until the queue fills up, after which time they could increase up to the max pool size (SimpleHttpServer.maxThreads == 150). But, requests from the client hang if there are no request threads available, so the queue size was not increasing. This left me at only 25 server threads max, which was not enough to provide much cpu utilization. The new server seems solid. I think it just needs facilties for dynamically managing threads based on configuration parameters and resource availability (e.g., message size). As mentioned before, I'm looking at adding those things. FYI, there are some left-over comments that are now obsolete, including the one about this not being production-quality, I hope. :-) > SimpleHttpServer based on Jakarta HttpComponents HttpCore > --------------------------------------------------------- > > Key: AXIS2-761 > URL: http://issues.apache.org/jira/browse/AXIS2-761 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: transports > Versions: 1.0 > Reporter: Oleg Kalnichevski > Attachments: jakarta-httpcore-4.0-20060521.jar, simplehttpserver.patch > > The following patch replaces the SimpleHttpServer implementation based on the > testing framework of Commons HttpClient 3.x with a one based on Jakarta > HttpComponents HttpCore. Compiled against Axis2 trunk and HttpCore trunk > * Removes all references to Commons HttpClient classes > * Enables streaming of schema definitions and similar content > * Improves content buffering of SOAP response > * Improves handling of fault conditions and exception handling > * Fixes a number of NPEs in AxisEngine > * Improves performance and reliability of the HTTP transport -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
