• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • core

      Upgraded from 1.599 to 1.614.
      JNLP slaves now fail to connect with following error, where <HOST> is my actual host.
      SSH slaves are unaffected.

      May 20, 2015 10:57:51 AM hudson.remoting.jnlp.Main$CuiListener error
      SEVERE: https://<HOST>/tcpSlaveAgentListener/ is invalid: 404 Not Found
      java.lang.Exception: https://<HOST>/tcpSlaveAgentListener/ is invalid: 404 Not Found
      at hudson.remoting.Engine.run(Engine.java:214)

          [JENKINS-28499] tcpSlaveAgentListener not found

          James Howe created issue -
          Daniel Beck made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163340 ] New: JNJira + In-Review [ 197175 ]
          Andreas Tscharner made changes -
          Resolution Original: Incomplete [ 4 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Oleg Nenashev made changes -
          Component/s Original: remoting [ 15489 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-38711 [ JENKINS-38711 ]
          Oleg Nenashev made changes -
          Labels New: remoting
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Labels Original: remoting New: remoting s
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-53461 [ JENKINS-53461 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]

            Unassigned Unassigned
            jameshowe James Howe
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: