On Wed, Jun 13, 2012 at 4:38 PM, Benson Margulies wrote:
>
> Does this suggest anything to anyone? Other than that we've
> misanalyzed the logic in the tokenizer and there's a way to make it
> burp on one thread?
it might suggest the different tokenstream instances refer to some
shared object tha
We've got a tokenizer which is quite explicitly coded on the
assumption that it will only be called from one thread at a time.
After all, what would it mean for two threads to make interleaved
calls to the hasNext() function()?
Yet, a customer of ours with a gigantic instance of Solr 1.4 reports
i