Pattern selector

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

  1. ObjectOutputStream.writeObject() has thrown a SocketException
    Java Runtime
  2. Connection force closed either by client or server causing write error
    Java Runtime

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames Connection reset by peer: socket write error
1 matching frame hidden
    at Source)
    at Source)
    at$BlockDataOutputStream.drain(Unknown Source)
    at$BlockDataOutputStream.setBlockDataMode(Unknown Source)
7 frames hidden


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. erocsvia GitHub2 days ago
    The last packet successfully received from the server was 47,917,5 51 milliseconds ago. The last packet sent successfully to the server was 47,917,551 milliseconds ago. is longer than the server configured value of ' wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
    Show stack trace
  2. stboissdevvia GitHub2 days ago
    Could not retrieve transaction read-only status from server
    Show stack trace
  3. gavinmhvia GitHub4 days ago
    Broken pipe (Write failed)
    Show stack trace
  4. thorstenwittvia GitHub4 days ago
    Broken pipe (Write failed)
    Show stack trace
  5. yinslvia GitHub4 days ago Broken pipe
    Show stack trace
  6. sshogunnvia GitHub5 days ago
    No message found for this stack trace.
    Show stack trace
  7. balousvia GitHub1 week ago
    There was a problem while connecting to
    Show stack trace
  8. cliviuvia GitHub1 week ago Connection reset by peer: socket write error
    Show stack trace