This also helps identify processes in top, htop etc. You can easily pkill or killall the correct JVM. In this example ps shows "java_my_app" instead of just "java". They create a symlink based on project name at runtime. My gradle projects don't call /bin/java directly. Process=`ps -ef | grep -v awk | awk -e '/java.*/ '` Replace the part with whatever java is executing. Here is a script one can use to automate the process. Jeff 11775 8890 6 08:59 pts/0 00:00:00 java TestProgramĪnd you wish to kill java TestProgram, you should run kill -9 11775. Java doesn't always stop when it receives a 'SIGTERM' signal (processes are allowed to handle 'SIGTERM'), so sending it the 'SIGKILL' signal, which makes init kill the program without warning it first, is often necessary.įor example, if ps -fC java returns UID PID PPID C STIME TTY TIME CMD Once you have the PID of the command you wish to kill, use kill with the -9 (SIGKILL) flag and the PID of the java process you wish to kill.
How to test java code for mac on linux full#
pgrep -a java will return the PID and full command line of each java process. You could also use pgrep to list all java processes. Here is the command in full: ps -fC java. That way, you can see what each java process is actually doing. You may also want to use ps's -f flag to print the full command name of each listed process. Instead of using ps and grep, you can use ps's -C flag to select all commands listed with the name 'java'.