Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

java.nio.channels.ClosedByInterruptException: null	at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)	at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:215)	at java.nio.channels.Channels.writeFullyImpl(Channels.java:78)	at java.nio.channels.Channels.writeFully(Channels.java:101)	at java.nio.channels.Channels.access$000(Channels.java:61)	at java.nio.channels.Channels$1.write(Channels.java:174)	at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)	at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)	at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)	at java.io.BufferedWriter.flush(BufferedWriter.java:254)	at org.eclipse.che.api.core.util.FileLineConsumer.writeLine(FileLineConsumer.java:41)	at org.eclipse.che.api.core.util.CompositeLineConsumer.writeLine(CompositeLineConsumer.java:45)	at org.eclipse.che.plugin.docker.machine.LogMessagePrinter.process(LogMessagePrinter.java:44)	at org.eclipse.che.plugin.docker.machine.LogMessagePrinter.process(LogMessagePrinter.java:26)	at org.eclipse.che.plugin.docker.client.LogMessagePumper.start(LogMessagePumper.java:80)	at org.eclipse.che.plugin.docker.client.DockerConnector.startExec(DockerConnector.java:543)	at org.eclipse.che.plugin.docker.machine.DockerProcess.start(DockerProcess.java:108)	at org.eclipse.che.api.environment.server.MachineProcessManager.lambda$exec$0(MachineProcessManager.java:121)