On Wed, Apr 22, 2009 at 5:06 PM, David Rees <[email protected]> wrote: > I would have expected to need to call > Stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED, > Boolean.FALSE) to get keep alive working from the documentation, but > then I realised that I'm not even seeing any chunked headers in the > request (it doesn't affect operation, either).
OK, more reading and now I realize that keep-alive should be on by default, but to get any performance benefit, I also need to REUSE_HTTP_CLIENT. So I've done that and yes, performance has improved now, but I run into the default limit of only 2 concurrent connections per host limit. How can I set my own MULTITHREAD_HTTP_CONNECTION_MANAGER or raise the default limit? This is a custom application so I am not worried about exceeding RFC specifications for concurrent connections. Is it as simple as Stub._getServiceClient().getOptions().setProperty(HTTPConstants.MULTITHREAD_HTTP_CONNECTION_MANAGER, myConnMan)? Are there any gotchas I should keep in mind? Thanks Dave
