David, if it's fast for you to reproduce, would it be possible for you
to try the latest Jetty 6.1.24 and see if the issue still exists?
http://dist.codehaus.org/jetty/
Seems like we should upgrade to 6.1.24 anyway (there were quite a few
fixes in 6.1.23)
http://jira.codehaus.org/secure/ReleaseNot
On 5/29/10 3:13 AM, Chris Hostetter wrote:
: Wow, thanks for the heads-up David!
: This probably got inadvertently changed when Jetty was upgraded...
: sounds like we should prob change back to BoundedThreadPool as a
: default!
it seems to have been a deliberate choice miler made, it was a dist
: Wow, thanks for the heads-up David!
: This probably got inadvertently changed when Jetty was upgraded...
: sounds like we should prob change back to BoundedThreadPool as a
: default!
it seems to have been a deliberate choice miler made, it was a distinct
commit 20 minutes after the jetty upgra
Wow, thanks for the heads-up David!
This probably got inadvertently changed when Jetty was upgraded...
sounds like we should prob change back to BoundedThreadPool as a
default!
-Yonik
http://www.lucidimagination.com
On Thu, May 27, 2010 at 5:43 PM, Smiley, David W. wrote:
> I'd like to warn peop
Please file a JIRA.
On Thu, May 27, 2010 at 2:43 PM, Smiley, David W. wrote:
> I'd like to warn people about the default configuration of Jetty in the Solr
> trunk release (not present in Solr 1.4 and prior). There is a difference in
> the jetty configuration which is for the latest Solr to us
