I've been working on getting Commons Configuration to be able to use VFS as its underlying file system and have everything working. However, in the course of this effort I ran into a problem. https://issues.apache.org/jira/browse/VFS-164 states that there were problems under load and so ThreadLocalHttpConnectionManager was written and replaced the use of MultiThreadedHttpConnectionManager.

The issue I ran into is that ThreadLocalHttpConnectionManager only allows a single connection open on a thread. This causes some fairly common use cases in Commons Configuration to fail. To get around this I have gone back to MultiThreadedHttpConnectionManager but provided mechanisms to configure maxConnectionsPerHost and maxTotalConnections. Doing this got, along with a few other changes, got everything to work.

What I'd like to know is, was there more to VFS-164 than is stated in the issue and is this change sufficient? Or do I need to create yet another HttpConnectionManager?

Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to