Hi,
I have good news (for me :), I have resolved my bug.
As always it was my own fault.
I did a few tests sometime ago so as to understand how instances of
various objects were instanciated in Lucene/Solr, and made a mistake in
understanding how SearchComponent were managed.
I believed that
Thanks for the answers,
I also found that blog post about such issues:
http://techbytes.anuragkapur.com/2014/08/potential-jetty-concurrency-bug-seen-in.html
On 01/07/15 20:26, Chris Hostetter wrote:
: Hmm, interesting. That particular bug was fixed by upgrading to Jetty
: 4.1.7 in https://issue
: Hmm, interesting. That particular bug was fixed by upgrading to Jetty
: 4.1.7 in https://issues.apache.org/jira/browse/SOLR-4031
1st) Typo - Shalin ment 8.1.7 above.
2nd) If you note the details of both issues, no root cause was ever
identified as being "fixed" -- all that hapened was that Pe
Hmm, interesting. That particular bug was fixed by upgrading to Jetty
4.1.7 in https://issues.apache.org/jira/browse/SOLR-4031
Solr uses Jetty 8.1.10.v20130312 in 5.0 but we upgraded further to
9.2.10.v20150310 in 5.2. Can you upgrade Solr to 5.2 and see if this
still reproduces? I'll also try to
Hello,
I'm new to the solr mailing list, and I have not used solr for much
time, so I might be wrong.
I may have found a bug whose symptoms look that one in jetty
https://bugs.eclipse.org/bugs/show_bug.cgi?id=392936
I am using solr 5.0.0 (the one with the great packaging and deployment
wor
