Issue1508

Running the attached file in Jython 2.5.1 causes the following to be 
thrown:

Exception in thread "_CouplerThread-1 (stdout)" Traceback (most recent 
call last):
  File "/usr/local/jython-2.5.1/Lib/subprocess.py", line 679, in run
    self.write_func(buf)
  File "/usr/local/jython-2.5.1/Lib/subprocess.py", line 679, in run
    self.write_func(buf)
ValueError: I/O operation on closed file

I can't reproduce this on OS X. What platform are you running on?

GNU/Linux x86, specifically Ubuntu 9.10.

Also, FWIW: $ java -version
java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.6.1) (6b16-1.6.1-3ubuntu1)
OpenJDK Client VM (build 14.0-b16, mixed mode)

I can't reproduce this on the Linux boxes I have access to, one running 
Sun Java x86_64, the other running OpenJDK x86

I don't see how this error could be triggered by this piece of code, 
that ValueError is only raised when calling a method on a closed Python 
file object. The subprocess module doesn't call close() on the files 
passed into it.

The stack trace is also odd, it suggests that write_func somehow ended 
up calling itself, which doesn't make any sense

Am I missing something here?

I get this exception in Win XP.

Exception in thread "_CouplerThread-2 (stdout)" Traceback (most recent call last):
  File "C:\jython2.7a2\Lib\subprocess.py", line 754, in run
    self.write_func(buf)
  File "C:\jython2.7a2\Lib\subprocess.py", line 754, in run
    self.write_func(buf)
ValueError: I/O operation on closed file

I also get the below error using Robotframework on Linux and Windows.

Exception in thread "_CouplerThread-5 (stdout)" Traceback (most recent call last):
  File "/home/seanog.oconaire/jython2.5.2/Lib/subprocess.py", line 675, in run
    self.write_func(buf)
  File "/home/seanog.oconaire/jython2.5.2/Lib/subprocess.py", line 675, in run
    self.write_func(buf)
ValueError: I/O operation on closed file

I cannot reproduce this issue on Windows 8.1, OS X 10.9, or Ubuntu 13.10, all running JDK 7.

Earlier JDKs had problems with process management, as we have seen in other reported bugs. This may be the case here.

I can still reproduce with Jython 2.5.3 on JDK7, can't reproduce with current tip.

Thanks, this does gives us a bit more insight. What OS version were you running this test case on?

This is on, unlike the above, Archlinux on x86_64, with the current Java package and the packaged Jython, which claims to be:

gsnedders@vanveen:~$ uname -a
Linux vanveen 3.14.6-1-ARCH #1 SMP PREEMPT Sun Jun 8 10:08:38 CEST 2014 x86_64 GNU/Linux
gsnedders@vanveen:~$ java -version
java version "1.7.0_60"
OpenJDK Runtime Environment (IcedTea 2.5.0) (Arch Linux build 7.u60_2.5.0-2-x86_64)
OpenJDK 64-Bit Server VM (build 24.60-b09, mixed mode)
gsnedders@vanveen:~$ /usr/bin/jython --version
Jython 2.5.3

Everything is current then with what gsnedders just reported, so no blaming old versions ;), except our own implementation of subprocess

Given the forthcoming release of 2.7, closing out. We are not going to be able to fix for 2.5 given our lack of resources.