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

HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)

    XMLWordPrintable

Details

    Description

      any cli command fails with exception. output attached. this output produced by create-job ommand, help command produces same.

      Attachments

        Issue Links

          Activity

            thesamet Nadav Samet added a comment - - edited

            I am still seeing "Protocol violation: Unexpected single newline character in chunk size' 0x0a" on Jenkins 1.549. Can you re-open?

            thesamet Nadav Samet added a comment - - edited I am still seeing "Protocol violation: Unexpected single newline character in chunk size' 0x0a" on Jenkins 1.549. Can you re-open?
            sstack S Stack added a comment - - edited

            @Jesse, 1.540 CLI is broken on Solaris.

            Feb 3, 2014 7:13:41 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run
            SEVERE: I/O error in channel Chunked connection to http://host.net:8080/cli
            hudson.remoting.DiagnosedStreamCorruptionException
            
            sstack S Stack added a comment - - edited @Jesse, 1.540 CLI is broken on Solaris. Feb 3, 2014 7:13:41 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://host.net:8080/cli hudson.remoting.DiagnosedStreamCorruptionException
            jglick Jesse Glick added a comment -

            @sstack might be a different bug, best to file separately (link to this one).

            jglick Jesse Glick added a comment - @sstack might be a different bug, best to file separately (link to this one).
            ashokm Ashok Manji added a comment - - edited

            @sstack - did you file a separate bug on this? I am also seeing this with v1.554.1 and the issue was not present when we were on v1.534

            ashokm Ashok Manji added a comment - - edited @sstack - did you file a separate bug on this? I am also seeing this with v1.554.1 and the issue was not present when we were on v1.534

            Same problem on 1.554.3. Is there a separate bug filed or not?

            mr_dfuse Nico Mommaerts added a comment - Same problem on 1.554.3. Is there a separate bug filed or not?

            People

              kohsuke Kohsuke Kawaguchi
              nkorotysh Nick Korotysh
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: