java.io.IOException

Stream closed

Samebug tips0

We couldn't find tips for this exception.

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

Solutions on the web75

Stack trace

  • java.io.IOException: Stream closed at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)[na:1.8.0_102] at java.io.BufferedWriter.write(BufferedWriter.java:221)[na:1.8.0_102] at java.io.Writer.write(Writer.java:157)[na:1.8.0_102] at org.eclipse.che.api.core.util.FileLineConsumer.writeLine(FileLineConsumer.java:38)[che-core-api-core-4.4.2.jar:4.4.2] at org.eclipse.che.api.core.util.CompositeLineConsumer.writeLine(CompositeLineConsumer.java:45)[che-core-api-core-4.4.2.jar:4.4.2] at org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:408)[che-core-api-machine-4.4.2.jar:4.4.2] at org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337)[che-core-api-machine-4.4.2.jar:4.4.2] at org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:165)[che-core-api-machine-4.4.2.jar:4.4.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startMachine(WorkspaceRuntimes.java:582)[che-core-api-workspace-4.4.2.jar:4.4.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.startQueue(WorkspaceRuntimes.java:458)[che-core-api-workspace-4.4.2.jar:4.4.2] at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.start(WorkspaceRuntimes.java:216)[che-core-api-workspace-4.4.2.jar:4.4.2] at org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$2(WorkspaceManager.java:551)[che-core-api-workspace-4.4.2.jar:4.4.2] at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28)[che-core-commons-lang-4.4.2.jar:4.4.2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_102] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_102]

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 visitor
Unknown visitorOnce,
Unknown visitor
Unknown visitorOnce,
Unknown visitor
Unknown visitorOnce,
tyson925tyson925
6 times, last one
Unknown visitor
Unknown visitorOnce,
2 more bugmates