• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

about thread

 
dx wu
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


this problem confuse me,and cloud someone help me? thanks
 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think A & E is the answer . I am sure about E .
 
dx wu
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Cloud explain the reason to me?
 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yaa sure ...
about E , we are just setting priority of thread ... so this method ( setPrority ) can't stop a thread to execution .

and other 3 except A are looking valid reason to stop execution ...
 
Mike Gershman
Ranch Hand
Posts: 1272
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would go with A and C.

Releasing a lock by exiting a synchronized block and releasing wait with notify might allow a higher priority thread to preempt the running thread, but that is indirect and conditional.

Setting another runnable thread to a higher priority will certainly cause one's own thread to stop running.
 
ankur rathi
Ranch Hand
Posts: 3830
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mike may be right ... sorry
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic