Are there system tools to find a runaway Confluence job process and end it?

[Laura Kolker]

Short story: Anyone know of any system tools that can be used to find a runaway Confluence chron/quartz job process and kill it?

Background:

We had a custom job module that was running fine for several months but it's gone off the rails. (It's a short running process, but its runs once a week, and it emails people.)

We tried disabling it in the Scheduled Jobs console.

It still ran.

We changed its configuration so it shouldn't email anyone. We cleared the plugins cache and did a reboot. We removed it wholesale from the plugin in which it came. The module flat-out isn't there anymore.

It still runs.

It's not generating logs either, even though it should be.

And to top it off, it seems like its behavior matches an earlier version rather than the one we released most recently in Nov.

We're willing try pretty much anything: system commands, plugin dev, REST.

I'm staring at Bob Swift's documentation to see if the Confluence CLI might help. 

Any ideas would be appreciated. Thanks!