Errors from log, occurs from time to time:

      Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle
      SEVERE: Failed to execute command Pipe.EOF(49) (channel qa3)
      java.lang.NullPointerException
              at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177)
              at hudson.remoting.Channel$2.handle(Channel.java:461)
              at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
      Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle
      SEVERE: This command is created here
      Command Pipe.EOF(49) created at
              at hudson.remoting.Command.<init>(Command.java:67)
              at hudson.remoting.Command.<init>(Command.java:50)
              at hudson.remoting.ProxyWriter$EOF.<init>(ProxyWriter.java:169)
              at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124)
              at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132)
              at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
              at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101)
              at java.lang.ref.Finalizer.access$100(Finalizer.java:32)
              at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190)
      

          [JENKINS-20769] Failed to execute command Pipe.EOF

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          pom.xml
          http://jenkins-ci.org/commit/jenkins/11458c956e64673d99a9dc2c05cfd5f9533b4e1b
          Log:
          [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/11458c956e64673d99a9dc2c05cfd5f9533b4e1b Log: [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core.

          mike bayer added a comment -

          just to update, I'm running "Jenkins ver. 1.558-SNAPSHOT (rc-04/01/2014 04:22 GMT-kohsuke)" which I assume includes this fix, I now see this in my logs:

          SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-34cf7b17))
          java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream
                  at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285)
                  at hudson.remoting.Channel$2.handle(Channel.java:461)
                  at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
          
          Apr 01, 2014 3:55:54 PM hudson.remoting.Channel$2 handle
          SEVERE: This command is created here
          Apr 01, 2014 3:57:13 PM hudson.remoting.Channel$2 handle
          SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-6ac87c49))
          java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream
                  at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285)
                  at hudson.remoting.Channel$2.handle(Channel.java:461)
                  at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
          
          

          not sure if this is related to the fix or not.

          mike bayer added a comment - just to update, I'm running "Jenkins ver. 1.558-SNAPSHOT (rc-04/01/2014 04:22 GMT-kohsuke)" which I assume includes this fix, I now see this in my logs: SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-34cf7b17)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Apr 01, 2014 3:55:54 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Apr 01, 2014 3:57:13 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-6ac87c49)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) not sure if this is related to the fix or not.

          Jesse Glick added a comment -

          Jesse Glick added a comment - @zzzeek added a note to @kohsuke’s commit: https://github.com/jenkinsci/remoting/commit/cdbc40b8980d3ea528473daf7e44475c956a9a03#commitcomment-5870985

          Resolved integrating remoting:2.36 in 75447b57b655e38fdb48f1e854a4b287071342cf.

          Oliver Gondža added a comment - Resolved integrating remoting:2.36 in 75447b57b655e38fdb48f1e854a4b287071342cf.

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          pom.xml
          http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec
          Log:
          [JENKINS-20769 JENKINS-20204] Integrating remoting 2.36

          Fixed a bug Jesse found in remoting

          (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf)

          Conflicts:
          pom.xml

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec Log: [JENKINS-20769 JENKINS-20204] Integrating remoting 2.36 Fixed a bug Jesse found in remoting (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf) Conflicts: pom.xml

          Ivaylo Bratoev added a comment - - edited

          This will make it in the next LTS version, right?
          Disregard - I found out what 1.554.1-fixed means Awaiting next LTS build release.

          Ivaylo Bratoev added a comment - - edited This will make it in the next LTS version, right? Disregard - I found out what 1.554.1-fixed means Awaiting next LTS build release.

          baz theman added a comment -

          Which version of jenkins includes the fix(es)?

          baz theman added a comment - Which version of jenkins includes the fix(es)?

          Andrew Erickson added a comment - - edited

          From scanning the changelog, 1.558 and later have the fix. LTS does not have it (not sure if it needs to be labeled lts-candidate to be picked up or not).

          Update: added the label

          Andrew Erickson added a comment - - edited From scanning the changelog, 1.558 and later have the fix. LTS does not have it (not sure if it needs to be labeled lts-candidate to be picked up or not). Update: added the label

          Was this really fixed in 1.554.1 (that's what the label means per https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line)? The changelog doesn't mention it.

          Andrew Erickson added a comment - Was this really fixed in 1.554.1 (that's what the label means per https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line)? The changelog doesn't mention it.

          aje: The LTS changelogs are not reliable in this regard. You are right to say that fix went into 1.554.1. See cloudbees changlog that tends to be accurate: http://release-notes.cloudbees.com/release/Jenkins+OSS+LTS/1.554.1

          Oliver Gondža added a comment - aje : The LTS changelogs are not reliable in this regard. You are right to say that fix went into 1.554.1. See cloudbees changlog that tends to be accurate: http://release-notes.cloudbees.com/release/Jenkins+OSS+LTS/1.554.1

            kohsuke Kohsuke Kawaguchi
            rprots Roman Prots'
            Votes:
            8 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: