Alexander V. Konstantinou writes:
> 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), brea
BAZLEY Sebastian wrote:
> In case anyone is interested, there is a useful description of such issues
> in the O'Reilly book "Java Threads", chapter 6 "Java Thread Scheduling",
> which discusses some popular scheduling implementations.
>
> A couple of suggestions (not tested):
>
> If you don't wan
: Java Mailing List
> Subject: Re: [Fwd: [Fwd: [Fwd: Swing Priority]]]
>
>
> 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,
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-sli
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 th
Setting my task to MIN_PRIORITY fixes the problem, but
I think it is a suboptimal fix. So:
a) What would a better priority be?
b) Is there a better fix than thread priority?
c) Does the event handling thread run at a lower priority than
the main applic
I guess I should of pointed out that I have already
tried the SwingWorker utility. I have tried various incarnations
of threading, using my real code and test code. If I have a
thread that does not sleep, then the main application locks up.
Using yield does not help. If I put a sleep
Does anyone know what the priority of the Swing
Event processing thread is? I have an application that needs to
process very large files, but I start the thread, the main
application is still locked up. Placing a yield() in the
time consuming thread doesn't seem to help. Any suggestion