Forcing a thread to stop

[sukatoa]

Good day,

I have a problem about trying to force the specific thread to stop while it is still waiting for a specific method to return.

By convention, having a flag inside the run method and by using it to return the said method is effective, but how about "still waiting to return the invoked method inside run method"?

sample:

public void run(){
String src = instance.getData();
}

where instance.getData() method will return after several minutes of waiting. I want to force that thread to stop ( since having a flag is not effective in that scenario ). Any other alternatives on how to reproduce this one?

Anybody?
I'm looking forward to your replies :)

[sukatoa]

ok, the interrupt method solves the problem(depends on how will it be implemented),

now, i want only the getData method to be stopped( while waiting for the returned value ) and not the succeeding instructions.

The alternative idea i could do is to throw that instruction in another thread and the succeeding instructions is also in another thread(waiting for a new value returned from getData through synchronized instance communication). But, i doubt to proceed hoping there's more convenient way to re-implement it. Any ideas?

[Steve11235]

What is getData() doing? Interrupting the thread only creates an exception if the thread is in a blocked state, such as a socket read. If getData() is blocking, the interrupting the thread will lead to an interruped exception. You can put a try/catch around the getData() call, or you could modify getData() to catch the exception.

[sukatoa]

it attempts to crawl the specific url and return its source(html)... some websites accept http connection but doesn't return any, that's why it will wait for how many minutes,hours...

So you mean, if an interrupt method invoked, the InterruptedException will be thrown from current instruction( getData )?

[sukatoa]

<duplicated>

[neilcoffey]

This sounds like the underlying thing you want to do is set a lower timeout on the socket, then?

[Steve11235]

Yes, in fact, it happens on the socket command that is waiting for a response. Neil's reply contains a good solution, if you have control over the socket buried inside getData(). You will still have to handle whatever happens when the socket times out (possibly an Exception).

If you can't modify the socket, I would suggest putting the getData() call in its own thread. I *think* you could use an inner class that implements Runnable, so that the class could easily pass the received data back to the thread starter as well as notify the thread starter that the task was complete. Have the thread starter wait for a specified time and then interrupt the thread if it has not returned. Of course, the thread starter itself will be blocked, and you will have synchronization issues to address.

[Mrs. Deswal]

Hi,


I was having same problem.
you can make this thread as daemon thread. Then the control will be in parent thread. So if you want to stop this thread after a certain interval of time then you can stop this thread from the thread where this thread is invoked.