| Author |
another help
|
wang jie
Greenhorn
Joined: May 01, 2002
Posts: 8
|
|
|
will the setPriority and exits synchronized code directly cause a thread to stop executing?
|
 |
Corey McGlone
Ranch Hand
Joined: Dec 20, 2001
Posts: 3271
|
|
Unfortunately, I haven't been able to find any documentation to back this up, but I believe that neither case will cause a thread to stop executing.
Corey
|
SCJP Tipline, etc.
|
|
Reid M. Pinchback
Ranch Hand
Joined: Jan 25, 2002
Posts: 775
|
|
It makes no sense for exiting a synchronized region to force a thread to stop executing. All a synchronized region says is "at the moment I need exclusive access to the object". The thread still has work to do when it isn't in a sync region, so there is no reason to force it to stop executing.
There really aren't any solid guarantees made about what priority even means, so there is no reason why changing it would force a thread to stop executing.
|
Reid - SCJP2 (April 2002)
|
|
 |
|
|
subject: another help
|
|
|
0
