java.io.IOException: The pipe is being closed


Solutions on the web248

Solution icon of bugzilla
via Eclipse Bugzilla by Darin_Swanson, 1 year ago
The pipe is being closed

Solution icon of github
via GitHub by wildfly-ci
, 1 year ago
The pipe is being closed

Solution icon of stackoverflow
via Stack Overflow by neon
, 11 months ago
The pipe is being closed

Solution icon of web
via codedmi.com by Unknown author, 1 year ago
The pipe is being closed

Solution icon of web
via dolinked.com by Unknown author, 1 year ago
The pipe is being closed

Solution icon of web
The pipe is being closed

Solution icon of web
The pipe is being closed

Solution icon of web
The pipe is being closed

Solution icon of web
The pipe is being closed

Solution icon of web
via epic-ide.org 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]

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

Samebug visitor profile picture
Unknown user
2 times, 1 year ago
Samebug visitor profile picture
Unknown user
2 times, 1 year ago
30 times, 1 month ago
8 times, 3 months ago
Once, 4 months ago
38 more bugmates