On Mon, Jun 27, 2011 at 1:11 PM, ChadDavis <[email protected]> wrote: > Note, I'm also running a patched version of the davex stack, on the > client of course, that allows for the number of http connections > created to be configured. Previously, we had witnessed only two > connections, and it was causing a bottleneck. Could we have uncovered > a concurrency issue with the webdav server now that we're hitting it > with more than two connections at once?
[Answering my own question . . . ] Yes, this comes from concurrency issues exposed by my performance patch that allow for more open connections in the davex transport layer ( webdav / http ).
