java.io.IOException

The pipe is being closed

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web14093

  • via GitHub by dbmalkovsky
    , 8 months ago
    The pipe is being closed
  • via nabble.com by Unknown author, 1 year ago
    The pipe is being closed
  • via codedmi.com by Unknown author, 1 year ago
    The pipe is being closed
  • Stack trace

    • java.io.IOException: The pipe is being closed at java.io.FileOutputStream.writeBytes(Native Method)[rt.jar:1.8.0_66] at java.io.FileOutputStream.write(FileOutputStream.java:326)[rt.jar:1.8.0_66] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)[rt.jar:1.8.0_66] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)[rt.jar:1.8.0_66] at java.io.FilterOutputStream.flush(FilterOutputStream.java:140)[rt.jar:1.8.0_66] at org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:125)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:137)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.stdin.Base64OutputStream.flush(Base64OutputStream.java:44)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.stdin.BaseNCodecOutputStream.close(BaseNCodecOutputStream.java:154)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.stdin.Base64OutputStream.close(Base64OutputStream.java:44)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:164)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:207)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler.java:140)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223)[jboss-as-process-controller-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[rt.jar:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[rt.jar:1.8.0_66] at java.lang.Thread.run(Thread.java:745)[rt.jar:1.8.0_66] at org.jboss.threads.JBossThread.run(JBossThread.java:122)[jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    2 times, 11 months ago
    Unknown user
    2 times, 1 year ago
    8 times, 2 weeks ago
    Once, 2 months ago
    Once, 2 months ago
    37 more bugmates