Trying to think what could cause an interrupt (other than another
thread calling .interrupt())... if it is the executor shutting down
early, perhaps some sort of reference counting issue on the core?
-Yonik
On Thu, Feb 26, 2009 at 5:40 PM, Ryan McKinley wrote:
> no core reloading. But this is a
no core reloading. But this is a non-standard core/schema loading
process.
Reverting to an older copy of solr/lucene makes this go away (at least
not show up)
any thoughts where to look? I have not looked too deeply.
ryan
On Feb 25, 2009, at 11:47 PM, Yonik Seeley wrote:
Hmmm, I don'
Hmmm, I don't believe Solr calls interrupt anywhere itself...
Would shutting down the executor cause that? Are you doing any core reloading?
-Yonik
http://www.lucidimagination.com
On Wed, Feb 25, 2009 at 6:01 PM, Ryan McKinley wrote:
> I just upgraded to /trunk from a nightly a few weeks ago.
I just upgraded to /trunk from a nightly a few weeks ago. I am now
seeing an error I did not see before:
2009-02-25 02:50:48,756 ERROR org.apache.solr.update.UpdateHandler -
java.lang.InterruptedException
at
java
.util
.concurrent
.locks.AbstractQueuedSynchronizer.acquireSharedI
