click below
click below
Normal Size Small Size show me how
OCPJP710.2
Cert Obj Manage and control thread lifecycle.
[10.2.1] Certification Objective | 10.2 Manage and control thread lifecycle. |
[10.2.2] Setting thread priorities (In this case, the program is trying to manipulate the scheduling of thread using priorities which is a bad idea. Simply because operating systems behave differently about priorities.) | For ex. Win32 uses Time Slicing i.e. it gives time to all the thread in proportion of their priorities but many unix systems do not let low priority threads run at all if a higher priority thread is running. So the output cannot be determined. |
[10.2.3]This question is based on a simple concept that calling Thread.sleep() does not release the lock. In this case, the first thread acquires the lock for the object and goes to sleep for 10 seconds. | Therefore, the second thread will not be able to get the lock to execute the second synchronized method until the first thread comes out of sleep (after 10 seconds) and releases the lock. |
[10.2.4]Thread is suspended or blocked (neither runnable nor dead) | ■ Sleeping ■ Waiting ■ Blocked because it needs an object's lock |
[10.2.5] Why would we use static Thread.sleep() | Because the thread is going too fast or wasting CPU cycles |