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

Samebug tips

  1. ,

    You are probably trying to write to a connection when the other end (the remote end of the connection) has already closed it.

  2. ,
    via by Unknown author

    Upgrade your docker-selenium Broken pipe	at Method)	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at	at cromwell.engine.backend.jes.Run.status(Run.scala:143)	at cromwell.engine.backend.jes.Run.checkStatus(Run.scala:156)	at cromwell.engine.backend.jes.JesBackend$$anonfun$poll$1$$anonfun$42.apply(JesBackend.scala:933)	at cromwell.engine.backend.jes.JesBackend$$anonfun$poll$1$$anonfun$42.apply(JesBackend.scala:933)	at scala.util.Try$.apply(Try.scala:192)	at cromwell.engine.backend.jes.JesBackend$$anonfun$poll$1.apply(JesBackend.scala:933)	at cromwell.engine.backend.jes.JesBackend$$anonfun$poll$1.apply(JesBackend.scala:927)	at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)	at scala.concurrent.impl.Future$	at	at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)	at scala.concurrent.forkjoin.ForkJoinTask.doExec(	at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(	at scala.concurrent.forkjoin.ForkJoinPool.runWorker(	at