Assuming this is on the master node, you could get thread stack traces from /threadDump (link in Manage Jenkins->System Information)
I believe it would be a thread labeled "Executor..."
I don't believe Jenkins can/will forcibly pull the rug out from under an executor. So if something about the job is in an infinite loop (probably plugin bug), it will not be able to be stopped.
If it is a slave elsewhere, I think the javameledy plugin can get slave stack traces, but not sure if you could install it and have it work without restarting. In this case, you could kill the process and jenkins should "do the right thing".
-
Thomas