Wild shot in the dark here, but try taking the
solrServer.commit() out and rely on the
autocommit parameters in solrconfig.xml.
And configure autocommit to commit, say,
every 5 minutes and do _not_ configure
the "numDocs" bit for autocommit.
If you do that and don't have this problem,
we can talk more about why but it'd
be a fast test.
Best
Erick
On Mon, Jun 17, 2013 at 4:03 AM, Snubbel
<solrforum.20.x...@spamgourmet.com> wrote:
> Hello,
>
> thanks for your replies,
>
> maybe I'm opening to many connections, only I don't know how, because I
> don't do this explicitly. Here is a snippet of my code, can anyone explain,
> where the connections are opend and how I can close them?
>
> solrServer = new HttpSolrServer(url);
> QueryResponse result = solrServer.query(query);
>
> for (SolrDocument doc : result.getResults()) {
> Map<String, Object> atomic_update_map_navigateTo = new
> HashMap<String, Object>();
> List<String> navigateToList = new ArrayList<String>();
>
> idList.add("ID123456789");
> atomic_update_map_navigateTo.put("add", idList);
>
> doc.setField("my_field_name", atomic_update_map_navigateTo);
>
> solrServer.add(ClientUtils.toSolrInputDocument(doc));
> commitCounter++;
> if (commitCounter % 50 == 0) {
> solrServer.commit();
> }
> }
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-Server-Add-causes-java-net-SocketException-No-buffer-space-available-tp4070533p4070943.html
> Sent from the Solr - User mailing list archive at Nabble.com.
