A followup: I discovered something interesting. If I don't run Jetty in the
same JVM as DirectSolrConnection, all is well.
Nrr.
Nope; in fact, I thought that might be the problem, so I spent some time to
make sure that I was (a) only loading a given core once, and (b) that all of
my setup/teardown was threadsafe.
So it's just one DirectSolrConnection for the lifetime of the application,
and it only gets closed when the JVM
This type of thing has come up in the past - check the searchable lists
(eg search.lucidimagination.com). Not sure there is much helpful there
though.
To be honest, this should *really* not be possible unless the executor
is in the SHUTDOWN state - which should really not be possible unless
c
This is one of those fantastically irritating bugs that only pops up...
sometimes. I'm using DirectSolrConnection to provide search for a JRuby
application, and everything works great, except every now and then, I get
a ava.util.concurrent.RejectedExecutionException in the error log.
I wrote a te
