[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection

[m...@wilfred.me.uk (JIRA)]

Wilfred Hughes commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection I've seen the same exception with a different header: Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31352D30 It turned out the cause was my Jenkins slave writing to the channel. My slave configuration was 'Launch slave via execution of the command on the master`, and my script set some JVM flags. The offending flags were: -XX:+PrintGCDetails -Xloggc:/foo/bar/jenkins_gc.log However, since the /foo/bar directory didn't exist, the JVM wrote GC logs to stdout. This resulted in the Stream seeing garbage. If you decode 31352D30 you get '15-01'. This is the start of a log line of the form: 2015-01-23T14:01:04.789+0000: 26.069: [CMS-concurrent-sweep-start] My workaround was to change my slave to launch via SSH, but I fixed it by ensuring that my GC log directory exists.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.