Java thread sleeps forever

Question

i am using the following code the problem i am facing is that the thread does not return from sleep only in one condition.can any one guide me regarding this.
can i know in what condition the java thread does not return after sleep.
while(ivIsActive)
// call some functions
try
Thread.currentThread().sleep(ivSleepTime * 1000);
catch (InterruptedException iException)
{ //............     }

Answer 1

wait (even with a timeout) and sleep really have
rather different functions and I'd be disinclined to
use wait where sleep was appropriate.If you ever what a sleep() to finish early use a wait().
If you try to interrupt a sleep there is no guarentee that this will not interrrupt in an unexpected place. With wiat you can be sure only thread waiting on a given object will receive the notify.
I almost never use sleep in preference for wait for this reason.
I consider it unwise to place much dependence on a notify not occuring, A notify should occur when you execute it. If you don't call notify, it doesn't.
you might use wait/notify on the object in question for some unrelated purpose
in different threads, forgetting this sleep. The notify should signify that a change has occured. The code should then test what has changed and what it should do about it. If you use this approach there is little impact in using the same notify for different purposes. If this is of real concern and you can use a dedicated object for notifying a change in the isAlive state (and make it private)
(I invariably use while tests before wait, rather than if tests).Could you clarify this point?
I think wait(time) should be regarded as a semaphore wait with timeout.I agreee. An if you want a Thread.run() loop to exit in a timely fashion then wait() is the thing to use. If you it is a requirement that the loop exit after the 30 second, then use sleep();
Anyway, as to the original problem I think you need
to make 500% sure that ivSleepTIme is what you think
it is (because I'd be extremely surprised if it is).
This is probably a good place for an assertion.I would also check that isAlive is really changing. It is not uncommon to be changing the isAlive in another context, or another object, or not at all.