Well this is hard to diagnose, but thus far, I've seen no reports of problems with thread factory w/o the wait(timeout)... I'm inclined to think that the JVMs were only having problems when the waitsets were rapidly being screwed with, as in 10s of thousands of threads being created and deleted every hour, which the changes to QThreadFactory and Edward's YThreadFactory both work to eliminate.
--Brandon On Tue, 10/28/03 at 00:33:17 -0600, Pascal wrote: > A bit ago toad went through all the code and added timeouts to all the > the waits. His commit notes included: > > apparently wait() can occasionally block forever on certain current > JVMs. So always use the form with an argument. > Don't use wait() anywhere, as the JVM has sadly been demonstrated to > occasionally lose notifications - always use a timeout > > I just noticed someone went into QThreadFactory an took out the > timeout. Was the timeout originally put there for a real JVM bug? The > synchronization problem certainly needed to be fixed, but does the bug > really exist? If so, we need to put that timeout back in. > > -Pascal > _______________________________________________ > Devl mailing list > [EMAIL PROTECTED] > http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
