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?
I don't *think* so... I haven't seen any trouble while load testing this on a real system. I *think* the RejectedExecutionException is thrown when JUnit aborts all execution. Essentially this is the ScheduledFutureTask saying "hey! i didn't get to complete even though you told me to"
