Performance bottle neck in Digir ProviderServlet
Now that each digir ecogrid query requests information from many different
providers (400 or so at any time), the performance of the Digir ProviderServlet
is a problem. In addition to the additional network hop between the ecogrid
DigirImpl and the Digir ProviderServlet, there are configuration issues in the
A stopgap measure is to throttle back the Ecogrid DigirImpl service to accepting
a reduced number of simultaneous connections.