any cli command fails with exception. output attached. this output produced by create-job ommand, help command produces same.
- is blocking
-
JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments
-
- Resolved
-
- is duplicated by
-
JENKINS-21209 any cli command fails with exception
-
- Resolved
-
- is related to
-
JENKINS-23232 Jenkins CLI: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A
-
- Resolved
-
I have narrowed this down to 1.535 and up; 1.534 is fine. This issue only occurs when "TCP port for JNLP slave agents" is set to Disabled.
My best guess is that the "two simultaneous HTTP connections" fallback for the CLI connection was broken with the introduction of Jetty8 in 1.535.
From the jenkins-cli output (similar to 2.log), one can with some effort decode the server side backtrace:
For the original submitter: you can workaround by re-enabling the JNLP port.