My guess on this is that you're making a LOT of database requests and have a
million TIME-WAIT connections, and your port range for local ports is
running out.
You should first confirm that's true by running netstat on the machine while
the load is running. See if it gives a lot of output.
One w
I don't think you can do this.
If you are sending multiple GET requests, you are doing it across different
HTTP connections. The web service has no way of knowing these are related.
One solution would be to pass a spare, unused parameter to your request,
like sequenceId=NNN and get the response
I have 300 cores so I feel your pain :-)
What we do is use a relative path for the file. It works if you use
../../common/schema.xml for each core, then just create a common directory
off your solr home and put your schema file there.
I found this works great with solrconfig.xml and all of it's
