If you read the JVM threading specification, it explicitely states that
threads of the same priority are *NOT* guaranteed to be time-sliced.
This is the most common cause of incompatibilities, as software that
works on MS WinNT (has time-slicing), breaks on other operating systems
without time-slicing. The solution is to have the busy thread execute
with a lower priority.
Alexander
On Tue, Jul 20, 1999 at 02:24:28PM -0400, Thomas M. Sasala wrote:
> It's not really a problem, unless the main app does something
> in an event that takes a while. Since I am currently the only one
> using the app, it's not an issue. However, in the future, it
> might become an issue.
>
> Generally I was hoping to set the thread to the same
> priority as the event handler and let the OS take care of
> time slicing. Clearly the JVM is not that robust though.
>
> "Robert A. Crawford" wrote:
> >
> > On Tue, Jul 20, 1999 at 12:32:19PM -0400, Thomas M. Sasala wrote:
> > > Setting my task to MIN_PRIORITY fixes the problem, but
> > > I think it is a suboptimal fix. So:
> >
> > Why is that a problem? The event thread probably spends
> > 95% of its time waiting for events, so your thread would get
> > the time it needs.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
