[JIRA] (JENKINS-49480) Close forcibly channel on StreamCorruptedException

[bat...@batmat.net (JIRA)]

Title: Message Title

Baptiste Mathus created an issue   Jenkins / JENKINS-49480 Close forcibly channel on StreamCorruptedException Issue Type: Improvement Assignee: Unassigned Components: remoting Created: 2018-02-09 14:57 Priority: Major Reporter: Baptiste Mathus On some cases, it can happen that the connection ends up in a very bad state, and it could throw a StreamCorruptedException and some stack trace like : WARNING: Failed to construct Command java.io.StreamCorruptedException: invalid stream header: 436C6173 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:857) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:349) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractByteBufferCommandTransport.processCommand(AbstractByteBufferCommandTransport.java:201) at hudson.remoting.AbstractByteBufferCommandTransport.receive(AbstractByteBufferCommandTransport.java:188) In such cases, there's few chance that the application will be written/designed to recover. In this case, Remoting should probably just forcibly terminate the connection, so that it gets reestablished cleanly from scratch. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.