*phew* I'd just written some code to test the "setPriority" behaviour and was worried about my understanding when I say the priority changing.
I guess K&B mean the JVM will not, for its own reasons, change the priority of a thread; they way it might, for its own reasons, yank a thread back to the Runnable pool or ignore "yield()".
posted 7 years ago
Tangentially related -and possibly outdated, applying to older JVM versions- I recall it being best practice not to change the priority of threads, because unpredictable and undesirable behavior might result. Sorry, I can't recall the details.
Skool. Stay in. Smartness. Tiny ad:
the new thread boost feature: great for the advertiser and smooth for the coderanch user