lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Snubbel <SolrForum.20.X...@spamgourmet.com>
Subject Re: Solr Server Add causes java.net.SocketException: No buffer space available
Date Mon, 17 Jun 2013 11:52:22 GMT
Hello,

I did set the autoCommit to 5 Minutes and removed all commit Statements but
one, because, you see, my test case is as follows:

I need a hugh number of documents in Solr. Then I want to update them with
AtomicUpdate and, for comparison, the "classical" way, like we did before
Solr 4.3. 
So, I need to do at least one hard commit to get the initial documents to
Solr and to be able to load them by query. 

That one commit already seems to be enough to cause the connections to
exceed.

Actually, the exception happens on adding the documents though, not on
commit:

solrServer.add(ClientUtils.toSolrInputDocument(docModule));
 
17.06.2013 13:45:44 org.apache.http.impl.client.DefaultRequestDirector
tryConnect
INFO: I/O exception (java.net.SocketException) caught when connecting to the
target host: No buffer space available (maximum connections reached?):
connect
17.06.2013 13:45:44 org.apache.http.impl.client.DefaultRequestDirector
tryConnect
INFO: Retrying connect
org.apache.solr.client.solrj.SolrServerException: IOException occured when
talking to server at: http://localhost:3333/solr-4.3.0
	at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:413)
	at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:180)
	at
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)
	at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:116)
	at org.apache.solr.client.solrj.SolrServer.add(SolrServer.java:102)
	at
de.exxcellent.connect.portal.business.solr.AtomicUpdateTest.addKontaktgehaeuseToModule(AtomicUpdateTest.java:234)
	at
de.exxcellent.connect.portal.business.solr.AtomicUpdateTest.performanceAtomicVSclassicUpdateTest(AtomicUpdateTest.java:41)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
	at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
	at org.testng.TestRunner.privateRun(TestRunner.java:767)
	at org.testng.TestRunner.run(TestRunner.java:617)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1123)
	at org.testng.TestNG.run(TestNG.java:1031)
	at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
	at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
	at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)
	at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:111)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
Caused by: java.net.SocketException: No buffer space available (maximum
connections reached?): connect
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:529)
	at
org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:127)
	at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
	at
org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294)
	at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
	at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
	at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
	at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
	at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
	at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:352)
	... 36 more


Any other ideas on what might be my problem here?

Best regards, Snubbel



--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-Server-Add-causes-java-net-SocketException-No-buffer-space-available-tp4070533p4070973.html
Sent from the Solr - User mailing list archive at Nabble.com.

Mime
View raw message