Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. Thread.run() has thrown a SocketException
    Java Runtime
    0
    0
    0
  2. Connection force closed either by client or server causing write error
    Java Runtime
    358
    275
    214

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
java.net.SocketException: Broken pipe
1 matching frame hidden
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
    at java.io.DataOutputStream.write(DataOutputStream.java:90)
5 frames hidden

Solution

poroszd3 years ago

Here is a animation for the life cycle.

Check the source of this solution for more info

External results for this pattern (10)

  1. balousvia GitHub2 days ago
    There was a problem while connecting to 10.64.120.18:22
    Show stack trace
  2. cliviuvia GitHub6 days ago
    java.net.SocketException: Connection reset by peer: socket write error
    Show stack trace
  3. adamrettervia GitHub1 week ago
    Broken pipe (Write failed)
    Show stack trace
  4. Omar Mezavia Google Groups1 week ago
    java.net.SocketException: Broken pipe
    Show stack trace
  5. Could not close connection: Broken pipe
    Show stack trace
  6. Arthur Nevesvia Google Groups1 week ago
    Broken pipe
    Show stack trace
  7. Omar Mezavia Google Groups1 week ago
    java.net.SocketException: Broken pipe
    Show stack trace
  8. Kunal Ghoshvia Google Groups1 week ago
    Broken pipe (Write failed)
    Show stack trace
  9. José Eduardo Trindade E Marquesvia Google Groups1 week ago
    Broken pipe (Write failed)
    Show stack trace