DK-7147084, fixed in 7u60. It would be good if you could
> check that update.
>
> -Alan.
>
--
Bruno Medeiros
https://twitter.com/brunodomedeiros
two processes where not even from the same executable, BTW). I
only changed it to cmd.exe for the sake of having a simpler example that
anyone could try, since cmd.exe is included with Windows.
--
Bruno Medeiros
https://twitter.com/brunodomedeiros
Any update on this? Has it been placed in the JVM bug database and/or have
people tried to replicated it? (again note, it only appears to happen on
JVM 7)
On Tue, May 6, 2014 at 9:20 PM, Bruno Medeiros
wrote:
> After much chopping, I have finally narrowed it down to a single source
> fil
After much chopping, I have finally narrowed it down to a single source
file, and no external dependencies (other than starting Windows' cmd.exe
process) :
https://github.com/bruno-medeiros/Scratchpad/blob/jvm-processio-issue/jvm_process_bug/src/JVMProcessBug.java
In this final form, I a
resolved.
On Wed, Apr 16, 2014 at 5:23 PM, Bruno Medeiros wrote:
> I have some code where I start an external process (ProcessBuilder.start()
> ,etc.) and then I spawn two worker threads to read the stdout and stderr of
> the external process. I directly read the streams provided by
&
using here:
https://github.com/bruno-medeiros/Scratchpad/tree/jvm-processio-issue
However, I haven't yet been able to replicate this bug using the isolated
code from there. At the moment, I can only replicate it when I run my full
application. The sample code could be simplified further, but I h
