Issue1868602

In Jython 2.2.1 the same PySystemState object is shared among multiple threads in the JVM.  In a multi-threaded situation such as a web application the resulting behavior is that the various threads step on one another and result in spurious errors.

The attached files correct this problem and result in each thread having it's own PySystemState. 

Note that a change was apparently made during the 2.2.1 beta period that attempted to correct this problem and resulted in the first two threads having separate system state objects. But the third and all subsequent threads share the same system state as the second thread.

File Added: ThreadStateMapping.java

File Added: ThreadStateMapping.diff

File Added: ThreadStateMapping2.diff

I'm not sure if this is the correct solution to get Jython running in multiple threads.  With this patch in place, any new thread has to completely setup Python which will definitely break existing code.  For the specific case of threads needing separate state, Py.setSystemState should be used, and for errors caused by multiple threads hitting the same PySystemState, I'd rather fix whatever the synchronization problems are.  What errors are you seeing?

Also, do you know the svn revision of the change you're referring to?  I'd like to see what it is.

I'm just merging all the patches into a single file per http://wiki.python.org/jython/PatchGuidelines
File Added: separate_pysystemstate_per_thread.diff

bflorian: are you still around and still interested in pushing this patch forward? Sorry it has lingered for so long.