groovy.lang.GroovyRuntimeException: exception while dumping process stream

Apache's JIRA Issue Tracker | Christopher Wong | 8 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Groovy provides convenience methods in Process like consumeProcessOutput that spawns off threads to handle an external process' I/O. Unfortunately, these threads are sort of dumped on the floor, leaving the user with no way to manage race conditions where threads finish at different times. For example, the following code tries to capture stdout into a compressed file: Process p = ['mysqldump', 'big_database'].execute() def os = new GZIPOutputStream(new File('dbdump.sql.gz').newOutputStream()) p.consumeProcessOutput os, System.err p.waitFor() os.close() This can result in the following exception. This is because while the process itself may terminate after Process.waitFor(), the thread writing the corresponding output stream may not be finished writing yet. So if I call OutputStream.close() immediately after Process.waitFor(), there is a chance that the gzip stream may not be fully written yet, so the consumer thread tries to write to an output stream that has already been closed. The trouble is, there is no way for me to tell when the consumer threads are done processing. Exception in thread "Thread-27" groovy.lang.GroovyRuntimeException: exception while dumping process stream at org.codehaus.groovy.runtime.DefaultGroovyMethods$ByteDumper.run(DefaultGroovyMethods.java:10063) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: write beyond end of stream at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:104) at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72) at org.codehaus.groovy.runtime.DefaultGroovyMethods$ByteDumper.run(DefaultGroovyMethods.java:10060) ... 1 more There are two possible solutions to this: 1. Process.waitFor should also wait for the consumer threads to finish. 2. Find a way to expose the consumer thread objects so the user can call Thread.join() on them.

    Apache's JIRA Issue Tracker | 8 years ago | Christopher Wong
    groovy.lang.GroovyRuntimeException: exception while dumping process stream
  2. 0

    Groovy provides convenience methods in Process like consumeProcessOutput that spawns off threads to handle an external process' I/O. Unfortunately, these threads are sort of dumped on the floor, leaving the user with no way to manage race conditions where threads finish at different times. For example, the following code tries to capture stdout into a compressed file: Process p = ['mysqldump', 'big_database'].execute() def os = new GZIPOutputStream(new File('dbdump.sql.gz').newOutputStream()) p.consumeProcessOutput os, System.err p.waitFor() os.close() This can result in the following exception. This is because while the process itself may terminate after Process.waitFor(), the thread writing the corresponding output stream may not be finished writing yet. So if I call OutputStream.close() immediately after Process.waitFor(), there is a chance that the gzip stream may not be fully written yet, so the consumer thread tries to write to an output stream that has already been closed. The trouble is, there is no way for me to tell when the consumer threads are done processing. Exception in thread "Thread-27" groovy.lang.GroovyRuntimeException: exception while dumping process stream at org.codehaus.groovy.runtime.DefaultGroovyMethods$ByteDumper.run(DefaultGroovyMethods.java:10063) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: write beyond end of stream at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:104) at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72) at org.codehaus.groovy.runtime.DefaultGroovyMethods$ByteDumper.run(DefaultGroovyMethods.java:10060) ... 1 more There are two possible solutions to this: 1. Process.waitFor should also wait for the consumer threads to finish. 2. Find a way to expose the consumer thread objects so the user can call Thread.join() on them.

    Apache's JIRA Issue Tracker | 8 years ago | Christopher Wong
    groovy.lang.GroovyRuntimeException: exception while dumping process stream
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    JSON Compression from JAX-RS in Glassfish

    Oracle Community | 6 years ago | ronak2121
    java.io.IOException: write beyond end of stream
  5. 0

    ADB Connection Error

    Stack Overflow | 4 years ago | Raveesh Lawrance
    java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:395) at com.android.ddmlib.Device.executeShellCommand(Device.java:462) at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      write beyond end of stream

      at java.util.zip.DeflaterOutputStream.write()
    2. Java RT
      GZIPOutputStream.write
      1. java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:104)
      2. java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72)
      2 frames
    3. Groovy
      DefaultGroovyMethods$ByteDumper.run
      1. org.codehaus.groovy.runtime.DefaultGroovyMethods$ByteDumper.run(DefaultGroovyMethods.java:10060)
      1 frame
    4. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:595)
      1 frame