How to Stop Java threads which are Running Infinitely

[Meet Gaurav]

Hi

I have a Java program that is developed using threads. Once we start the java program using “java classname” that will infinitely looking into the IBM MQ. Currently we are killing the process to stop the service. Someone Please assist me to stop the javathread using the command line itself.

Or I can write another java program to stop or interrupt the thread which is running infinitely.

Please assist me.

[Srikanth Nalam]

Hi Meet,

If you are using windows OS, you can use (PS tools) pskill.exe to kill a process.

Google to download and usage.

[Meet Gaurav]

Sorry It's Unix Server

[Peter van de Riet]

If you can put yourself messages on the queue, you can add a "STOP" message.
Or you can add a "control queue" where you send messages to, this can also be used to send other controls, like for instance loglevel.

[Meet Gaurav]

   
public class TestStop {

	static boolean flag = false;
	
	public static void main(String[] args)
	{
		for(;;)
		{
			if(flag)
			   System.out.println("IF");
			else
				System.out.println("ELSE");
		}
		
	}
}

 

From another class I tried setting the flag = true.. But no use...Please assit me

[Rob Spoor]

That's because the other program has another JVM instance, so another instance of the class. The two "flags" are unrelated.

Search around for interprocess communication. Usual ways are using sockets, files, mapped memory, ..

Using a file it could be easy, but I don't know if the following code will run into synchronization problems. That's up to the file system probably.
Original process:

File file = new File(...);
file.createNewFile();
while (file.exists())
{
    ...
}

Stopping process:

File file = new File(...); // same file of course
file.delete();

On Unix / Linux, /var/run/XXX.pid (replace XXX with your application name) is a file used regularly, although it usually contains the process ID of the actual process.

[Manish Singh]

why depending on the existence of the file.

use the property like

keepRunning=true

in some property file

[Rob Spoor]

That would work as well but it would require the file to be actually read. It may even be absent. If that's the only content then checking for the file's presence is faster. Your solution is more scalable though; if you get more properties you can simply add them to the file.