Title: Provide PythonInterpreter#abort to interrupt Jython execution
Type: Severity: major
Components: Core Versions: Jython 2.7
Status: open Resolution: accepted
Dependencies: Superseder:
Assigned To: Nosy List: andrewparks, zyasoft
Priority: Keywords:

Created on 2016-10-26.22:42:29 by andrewparks, last changed 2016-10-30.20:17:18 by andrewparks.

msg10973 (view) Author: Andrew (andrewparks) Date: 2016-10-26.22:42:28
Scenario: I use Jython to call the popular, which will sometimes go into an endless processing loop for some malformed news feeds

Current fix: I have to write code to "kill -9" the Java process and restart it every 10 minutes so that endless Jython execution threads don't block all available execution threads

Proposed fix: Implement some way to notify Jython to abort execution of whatever python it is running

msg10974 (view) Author: Andrew (andrewparks) Date: 2016-10-26.22:44:15
Alternate fix: Implement a timeout parameter which instructs jython to abort execution after a certain amount of time has passed
msg10975 (view) Author: Jim Baker (zyasoft) Date: 2016-10-27.12:20:21
Just to be clear: SIGTERM does not work for you?
msg10976 (view) Author: Andrew (andrewparks) Date: 2016-10-27.13:25:19
Hi Jim, I didn't mean to imply that 'kill -9' was the only way to terminate the Java process from the command line. I'm sure I could have used SIGTERM instead of SIGKILL.

The issue is that where there is a PythonInterpreter.exec() in progress in a Java thread, there is no way for any other Java thread to halt execution in that thread.

Therefore, as it currently stands, the only way to stop a PythonInterpreter.exec() call which refuses to return is to kill the entire Java process on the command line, killing not only the long running PythonInterpreter.exec() but all other Java threads too.
msg10977 (view) Author: Andrew (andrewparks) Date: 2016-10-27.14:04:33
What I'm suggesting is some kind of PythonInterpreter.abort() method so that out of control infinite loop python scripts being executed via PythonInterpreter.exec() can be stopped.

Without a feature like this, Jython is basically unusable in production if any non returning PythonInterpreter.exec() calls start to pile up.
msg10978 (view) Author: Jim Baker (zyasoft) Date: 2016-10-27.14:37:08
Presumably we can implement PythonInterpreter#abort using a similar approach to org.python.util.jython#shutdownInterpreter, but to set the restart flag for a specific PySystemState, not the current state as defined by a thread local.

    public static void shutdownInterpreter() {
        // Stop all the active threads and signal the SystemRestart
        Py.getSystemState()._systemRestart = true;
        // Close all sockets -- not all of their operations are stopped by
        // Thread.interrupt (in particular pre-nio sockets)
        try {
        } catch (PyException pye) {
            // continue

Note that we should be able to do a better cleanup in  as of Jython 2.7 and recent Java - assuming well behaved resources.
msg10979 (view) Author: Andrew (andrewparks) Date: 2016-10-27.14:59:13
Jim, thank you so much for your responses. I did not realise until you pointed it out that it was possible to interrupt a PythonInterpreter.exec() by simply doing a Thread.interrupt().

I was not aware of shutdownInterpreter(), and it seems to be the solution I was looking for. In fact, I didn't even realise from the Jython docs that I could use Thread.interrupt() to abort execution.

Thank you very much for helping me understand how to resolve this problem now. So although I know to fix my issue, a way to shutdown reset the PythonInterpreter rather than simply shut it down is still very welcome.

FYI, for anyone else coming across this page, here is the code that I didn't realise until now that I could have written to abort PythonInterpreter.exec():

PythonInterpreter pi = new PythonInterpreter();

    Thread jythonThread = new Thread(new Runnable() {
      public void run() {
        pi.exec("while 1: print 'hello'");


    new Thread(new Runnable() {
      public void run() {
        try {
        catch (InterruptedException e) {
msg10980 (view) Author: Jim Baker (zyasoft) Date: 2016-10-27.15:03:26
Thread interruption from Python itself is also discussed here:

We need to update the book to discuss functionality that has since become part of Jython 2.7.
msg10981 (view) Author: Jim Baker (zyasoft) Date: 2016-10-28.09:31:57
This should also attempt a cleanup of the corresponding PySystemState in terms of any corresponding threads and files (including sockets).

It is possible that #abort should be on PySystemState itself, instead of the PythonInterpreter.
msg10982 (view) Author: Andrew (andrewparks) Date: 2016-10-30.20:17:17
This is way worse a situation that I'd thought - I'd assumed so far that I could just call thread.interrupt and abort any PythonInterpreter.exec() and then just create new PythonInterpreters and carry on.

This is not the case - after a thread.interrupt(), the whole VM is broken and cannot exec any more python, even if new PythonInterpreters are instantiated!!

Sample code that demonstrates the problem:

    PythonInterpreter pi = new PythonInterpreter();

    Thread jythonThread = new Thread(() -> {
      try {
        pi.exec("while 1: print 'hello'");
      catch (org.python.core.PyException e) {
        PythonInterpreter pi2 = new PythonInterpreter();
        pi2.exec("print 'hello again'"); // THROWS a org.python.core.PyException - WHY?!


    new Thread(() -> {
      try {
      catch (InterruptedException e) {
Date User Action Args
2016-10-30 20:17:18andrewparkssetmessages: + msg10982
2016-10-28 09:31:57zyasoftsetmessages: + msg10981
2016-10-28 09:30:03zyasoftsetresolution: accepted
title: Jython execution cannot be aborted -> Provide PythonInterpreter#abort to interrupt Jython execution
2016-10-27 15:03:26zyasoftsetmessages: + msg10980
2016-10-27 14:59:14andrewparkssetmessages: + msg10979
2016-10-27 14:37:09zyasoftsetmessages: + msg10978
2016-10-27 14:04:34andrewparkssetmessages: + msg10977
2016-10-27 13:25:20andrewparkssetmessages: + msg10976
2016-10-27 12:20:22zyasoftsetnosy: + zyasoft
messages: + msg10975
2016-10-26 22:44:15andrewparkssetmessages: + msg10974
2016-10-26 22:42:29andrewparkscreate