RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-10-19 Thread Markus Jelsma
sma <markus.jel...@openindex.io> > Sent: Thursday 19th October 2017 13:45 > To: solr-user@lucene.apache.org > Subject: RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace > > Hello, > > We are having this problem again, now it affects the front-end too, the logs

RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-10-19 Thread Markus Jelsma
; To: solr-user@lucene.apache.org > Subject: Re: SolrJ 6.6.0 Connection pool shutdown now with stack trace > > On 7/18/2017 5:10 AM, Markus Jelsma wrote: > > The problem was never resolved but Shawn asked for the stack trace, here it > > is: > > > Caused by: java.lang.Ill

Re: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Shawn Heisey
On 7/18/2017 5:10 AM, Markus Jelsma wrote: > The problem was never resolved but Shawn asked for the stack trace, here it > is: > Caused by: java.lang.IllegalStateException: Connection pool shut down > at org.apache.http.util.Asserts.check(Asserts.java:34) As I suspected, it is the connection

RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Markus Jelsma
ey are clean. > > > > Thanks, > > Markus > > > > > > > > -Original message- > > > From:Susheel Kumar <susheel2...@gmail.com> > > > Sent: Tuesday 18th July 2017 14:30 > > > To: solr-user@lucene.apache.org > > > Subject: Re: So

Re: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Susheel Kumar
l.com> > > Sent: Tuesday 18th July 2017 14:30 > > To: solr-user@lucene.apache.org > > Subject: Re: SolrJ 6.6.0 Connection pool shutdown now with stack trace > > > > Do you see any errors etc. in solr.log during this time? > > > > On Tue, Jul 18, 2017

RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Markus Jelsma
Hello Susheel, No, nothing at all. I've check all six nodes, they are clean. Thanks, Markus -Original message- > From:Susheel Kumar <susheel2...@gmail.com> > Sent: Tuesday 18th July 2017 14:30 > To: solr-user@lucene.apache.org > Subject: Re: SolrJ 6.6.0 Connection

Re: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Susheel Kumar
mentioned there is no firewall limiting > connections between those hosts. Actually, the processes run on the same > hosts as the Solr cluster is running on. > > > > Thanks, > > Markus > > > > > > > > -Original message- > > > From:Alexandre Raf

RE: SolrJ 6.6.0 Connection pool shutdown now with stack trace

2017-07-18 Thread Markus Jelsma
nt: Thursday 29th June 2017 16:38 > To: solr-user@lucene.apache.org > Subject: RE: SolrJ 6.6.0 Connection pool shutdown > > Thanks. I probably should have mentioned there is no firewall limiting > connections between those hosts. Actually, the processes run on the same > hosts

RE: SolrJ 6.6.0 Connection pool shutdown

2017-06-29 Thread Markus Jelsma
t; > Sent: Thursday 29th June 2017 15:38 > To: solr-user <solr-user@lucene.apache.org> > Subject: Re: SolrJ 6.6.0 Connection pool shutdown > > One thing to check is whether there is a firewall between the client > and the server. They - sometimes - cut the silent connections i

Re: SolrJ 6.6.0 Connection pool shutdown

2017-06-29 Thread Alexandre Rafalovitch
'll let it print the stack trace and get back if it happens again. > > Thanks, > Markus > > -Original message- >> From:Shawn Heisey <apa...@elyograg.org> >> Sent: Tuesday 27th June 2017 23:02 >> To: solr-user@lucene.apache.org >> Subject: Re: Sol

RE: SolrJ 6.6.0 Connection pool shutdown

2017-06-29 Thread Markus Jelsma
t; > Sent: Tuesday 27th June 2017 23:02 > To: solr-user@lucene.apache.org > Subject: Re: SolrJ 6.6.0 Connection pool shutdown > > On 6/27/2017 6:50 AM, Markus Jelsma wrote: > > We have a proces checking presence of many documents in a collection, just > > a simple cli

Re: SolrJ 6.6.0 Connection pool shutdown

2017-06-27 Thread Shawn Heisey
On 6/27/2017 6:50 AM, Markus Jelsma wrote: > We have a proces checking presence of many documents in a collection, just a > simple client.getById(id). It sometimes begins throwing lots of these > exceptions in a row: > > org.apache.solr.client.solrj.SolrServerException: >