On 2/4/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
Stack trace:
INFO: Opening [EMAIL PROTECTED] main
Feb 4, 2007 5:19:41 PM org.apache.solr.core.SolrException log
SEVERE: java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1477)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:384)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:856)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:45)
at
java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:606)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:486)
at
org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:514)
at
org.apache.solr.update.DirectUpdateHandler2$CommitTracker.run(DirectUpdateHandler2.java:625)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:65)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:168)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Getting the test to pass is one thing... but this exception is
another. Is it possible that this could be triggered by normal use of
Solr? Perhaps by too-frequent commits?
-Mike
