Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-595

I/O error in channel locally launched channel on

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • remoting
    • None
    • Platform: All, OS: Linux

      Quite often my builds fail with no messages in 'Console Output', but this in the
      catalina.out:

      13-Jun-2007 12:10:08 hudson.remoting.Channel$ReaderThread run
      SEVERE: I/O error in channel locally launched channel on [Ljava.lang.String;@153c350
      java.io.IOException: Stream closed
      at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:239)
      at
      java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2196)
      at
      java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2486)
      at
      java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2496)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
      at hudson.remoting.Channel$ReaderThread.run(Channel.java:377)

      These tend to be 'pom' projects, which just group other modules. The child
      modules build correctly. Any hints on how to debug this?

      (PS: thanks for all your help - excellent service!)

          [JENKINS-595] I/O error in channel locally launched channel on

          I guess for some reasons the launched Maven process have failed, but Hudson
          didn't receive any output from it in time and hence the console output is empty.

          I modified code in 1.116 so that it displays the command line options used to
          launch maven (the same should be available in the console output — was your
          console output really really empty?)

          If anyone can provide any further info, that would be great.

          Kohsuke Kawaguchi added a comment - I guess for some reasons the launched Maven process have failed, but Hudson didn't receive any output from it in time and hence the console output is empty. I modified code in 1.116 so that it displays the command line options used to launch maven (the same should be available in the console output — was your console output really really empty?) If anyone can provide any further info, that would be great.

          I think I fixed the problem. In 1.117.

          Kohsuke Kawaguchi added a comment - I think I fixed the problem. In 1.117.

            Unassigned Unassigned
            tal tal
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: