Re: java.net.SocketException: Connection reset

On 7/7/2014 7:30 AM, heaven wrote: > Yeah. the heap is huge, need to optimize the caches. It was 8Gb previously, > had to increase because there were out of memory errors. Using > ConcMarkSweepGC, which is supposed to not lock the world. At one time the only thing I was using that was non-default

Re: java.net.SocketException: Connection reset

net.SocketException: Connection reset > at java.net.SocketInputStream.read(SocketInputStream.java:196) > at java.net.SocketInputStream.read(SocketInputStream.java:122) > at > > org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSession

Re: java.net.SocketException: Connection reset

Yeah. the heap is huge, need to optimize the caches. It was 8Gb previously, had to increase because there were out of memory errors. Using ConcMarkSweepGC, which is supposed to not lock the world. Had to disable optimize (previously we did so by a cron task) because the index is big and optimize h

Re: java.net.SocketException: Connection reset

I don't see anything out of the ordinary thus far, except your heap looks a little big. I usually run with 6-7gb. I'm wondering if maybe you're running into a juliet pause and that's causing your sockets to time out. Have you gathered any GC stats? Also, what are you doing with respect to commits

Re: java.net.SocketException: Connection reset

Today this had happened again + this one: null:java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) at java.net.SocketOutputStream.write(SocketOutputStream.jav

Re: java.net.SocketException: Connection reset

Hello, usually the loading is not high at all: We're using bundled jetty and writing in batches by 50-100 documents and only using soft and auto commits. About clients, we have 4 processes and each could run up to 5 threads. At

Re: java.net.SocketException: Connection reset

2:06 PM, heaven wrote: > Hi, trying DigitalOcean for Solr, everything seems well, except sometimes I > see these errors: > java.net.SocketException: Connection reset > at java.net.SocketInputStream.read(SocketInputStream.java:196) > at java.net.SocketInput

java.net.SocketException: Connection reset

Hi, trying DigitalOcean for Solr, everything seems well, except sometimes I see these errors: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:196) at java.net.SocketInputStream.read(SocketInputStream.java:122) at

RE: "Caused by: java.net.SocketException: Connection reset by peer: socket write error" solr querying

t error to show up in the logs and what happens client side when you see the error? -Original Message- From: aniljayanti [mailto:aniljaya...@yahoo.co.in] Sent: Sunday, August 25, 2013 11:28 PM To: solr-user@lucene.apache.org Subject: RE: "Caused by: java.net.SocketException: Conn

RE: "Caused by: java.net.SocketException: Connection reset by peer: socket write error" solr querying

java.lang.Thread.run(Thread.java:662) Caused by: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at

RE: "Caused by: java.net.SocketException: Connection reset by peer: socket write error" solr querying

Greg -Original Message- From: aniljayanti [mailto:aniljaya...@yahoo.co.in] Sent: Thursday, August 22, 2013 11:44 PM To: solr-user@lucene.apache.org Subject: "Caused by: java.net.SocketException: Connection reset by peer: socket write error" solr querying Hi, I am working on

"Caused by: java.net.SocketException: Connection reset by peer: socket write error" solr querying

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:662) Caused by: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method)

java.net.SocketException: Connection reset

tException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149) at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:111)

Re: Error java.net.SocketException: Connection reset with longer Solr Query

I don't think it is true that Slr 1.3 uses only GET. The SolrJ API lets you choose which http method you wish to use On Sat, May 2, 2009 at 3:40 AM, ANKITBHATNAGAR wrote: > > Hi Guys > Solr 1.3 only uses GET never uses POST. > > So I started using Sol4 1.4 nightly build for now. > > Ankit > -- >

Re: Error java.net.SocketException: Connection reset with longer Solr Query

Hi Guys Solr 1.3 only uses GET never uses POST. So I started using Sol4 1.4 nightly build for now. Ankit -- View this message in context: http://www.nabble.com/Error--java.net.SocketException%3A-Connection-reset-with-longer-Solr-Query-tp23322549p23340562.html Sent from the Solr - User mailing

Re: Error java.net.SocketException: Connection reset with longer Solr Query

yote.http11.Http11Processor.process(Http11Processor.java:845) >        at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) >        at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >        at java.l

Re: Error java.net.SocketException: Connection reset with longer Solr Query

tandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proc

Error java.net.SocketException: Connection reset

lve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11P