PoolingHttpClientConnectionManager maxConnections causing issues

As I understand it, this servlet does not provide a way to increase the max connections or max connections per route on the PoolingHttpClientConnectionManager. As a result, a few long running requests from a handful of clients can quickly cause connections for all clients to hang until the long running requests complete. As far as I could tell, there's no obvious way to change the values of those two properties in the library.
I created a fork to allow setting both of them to custom values (though since it is one route per servlet, I probably could have just used a single init param to set both values). Should I create a pull request, or is there another, better way to set the max connections?

Start by locating the servlet code that creates and configures PoolingHttpClientConnectionManager, then review how its maximum connections and maximum connections per route are set. Check the proposed fork mentioned in the issue for the intended configuration approach, and verify that concurrent long-running requests no longer prevent other clients from obtaining connections.