Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove Ads
Don't know
Know
remaining cards
Save
0:01
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards




share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  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
Created by: MVK2013