On Thu, Mar 1, 2012 at 5:20 PM, Dawid Weiss <[email protected]> wrote: > Overriding toString on a Thread is not a good idea. Can I remove it or > at least make it simpler in ConcurrentMergeScheduler? This override > caused a fantastic deadlock -- an interesting possibility I didn't > think of -- again, when dumping threads (for the exception string) > Thread.toString was invoked from what I thought was an isolated > monitor (and it was); only toString had its own monitors underneath > and here's what happened (simplified):
Ouch! Now I've got to go think if we've done anything like that in Solr... -Yonik lucenerevolution.com - Lucene/Solr Open Source Search Conference. Boston May 7-10 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
