I get the same error when on the linux box, in the wrapper log I get:
INFO | jvm 1 | 2009/05/04 22:30:14 | May 4, 2009 10:30:14 PM hudson.remoting.Channel$ReaderThread run
INFO | jvm 1 | 2009/05/04 22:30:14 | SEVERE: I/O error in channel HTTP full-duplex channel aac41a55-56f6-4709-9913-af6d9f5091ea
INFO | jvm 1 | 2009/05/04 22:30:14 | java.io.StreamCorruptedException: invalid type code: 0D
INFO | jvm 1 | 2009/05/04 22:30:14 | at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1356)
INFO | jvm 1 | 2009/05/04 22:30:14 | at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
INFO | jvm 1 | 2009/05/04 22:30:14 | at hudson.remoting.Channel$ReaderThread.run(Channel.java:727)
INFO | jvm 1 | 2009/05/04 22:30:14 | May 4, 2009 10:30:14 PM hudson.model.FullDuplexHttpChannel$1 onDead
INFO | jvm 1 | 2009/05/04 22:30:14 | INFO: Duplex-HTTP session aac41a55-56f6-4709-9913-af6d9f5091ea is terminated

We suspect this error depends on the servlet container, so please report how you
run the server.

The wrapper just starts the included winstone container.

Regards
Mirko

assigned the issue to the proper component

[for your reference] We are in similar but slightly different? trouble. @see JENKINS-7052

Thanks, Tksh

I believe this is the same issue as JENKINS-11130. The fix for this was recently committed and should be in 1.440. If you are still willing/able then please re-test against 1.440 and report back. Otherwise I will close as this as a duplicate of 11130.

I am still receiving this error using Jenkins 1.444 and java 1.6.0_29

Exception in thread "main" java.io.IOException: Premature EOF
at sun.net.www.http.ChunkedInputStream.readAheadBlocking(ChunkedInputStream.java:538)
at sun.net.www.http.ChunkedInputStream.readAhead(ChunkedInputStream.java:582)
at sun.net.www.http.ChunkedInputStream.read(ChunkedInputStream.java:669)
at java.io.FilterInputStream.read(FilterInputStream.java:116)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2676)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2671)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2660)
at hudson.remoting.Channel.<init>(Channel.java:406)
at hudson.remoting.Channel.<init>(Channel.java:366)
at hudson.remoting.Channel.<init>(Channel.java:327)
at hudson.remoting.Channel.<init>(Channel.java:323)
at hudson.remoting.Channel.<init>(Channel.java:311)
at hudson.cli.CLI.connectViaHttp(CLI.java:124)
at hudson.cli.CLI.<init>(CLI.java:107)
at hudson.cli.CLI.<init>(CLI.java:85)
at hudson.cli.CLI._main(CLI.java:300)
at hudson.cli.CLI.main(CLI.java:245)

Brian, Many thanks for taking the time to test this. Looking at your stack trace it does seem a little different to JENKINS-11130 the channel constructor is not completing so the PingThread at CLI.java:126 is not getting started.

The Channel startup is stuck at Channel.java:406 which is where the read side code is waiting for the remoting preamble to be sent by the server.

Are there any related error messages in the jenkins server log file. That may give clues as to what the server is seeing and why it is closing the read side connection.

Do you have a virus scanner running on the client machine. It maybe that a virus scanner is intercepting the HTTP stream and buffering the data. This would stop the cli program receiving the output from the server and would cause a timeout as seen above. If possible it would be good to test with any virus scanners disabled.

No response from the submitter (3-years timeout).

There have been fixes to this around ~1.550. Installing a new version may help.

If something like this occurs on recent Jenkins, please file a new issue, don't just reopen this one.
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue