Roedy said:
Technopeasants have a rough time shutting down a failed java app. They
have to hit crtl-alt-delete, find the task in a jumping list
(which might contain several tasks named java.exe), and delete it.
Is there something easier, something that could be invoked by just
clicking an icon to kill a job?
Not without rolling your own.
It depends on your runtime platform, etc. One thing we do at my job is
create standard "start up" scripts that create PID files, then you know
the process id of the job you just started. This is a little more
simple in the bash/Unix/Linux environment, but I'm pretty sure it is
possible in Windows.
Another solution we've implemented is to basically embed any standalone
process/program with a socket listener (this needs to be a seperate
thread in case your main thread is hung, etc, you still need be able to
access the process. You can assign the port that the socket listener
listens to, in a config file at start up time. Then you implement a
known set of commands (check, start, stop, kill, etc.) that you can
issue on that socket (via a client you also have write). Then you can
administer the daemon/process via this admin client.
