• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • remoting
    • None
    • Jenkins 2.282 weekly

      For some time (probably quite a while and possibly a long time) the reconnect mechanism involving a "cookie" has not been working correctly for TCP-connected agents (JNLP). Perhaps it never worked correctly for all or some of the protocols.

      The impact is quite negligible, as by itself this mechanism accomplishes little. Pretty much all it does, would still need to be protected by other mechanisms. As one piece of robustness and retries, it provides some value. Getting it working again could provide some benefit, particularly in clearing up confusing for people reading logs.

          [JENKINS-64510] [remoting] Issues with TCP agent reconnects

          Jeff Thompson created issue -

          Jeff Thompson added a comment -

          Jeff Thompson added a comment - See https://github.com/jenkinsci/remoting/pull/429 and https://github.com/jenkinsci/jenkins/pull/5138 for the current status on improving this behavior.
          Mark Waite made changes -
          Remote Link New: This issue links to "Included in Jenkins 2.282 weekly (Web Link)" [ 26532 ]
          Mark Waite made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Fixed but Unreleased [ 10203 ]
          Mark Waite made changes -
          Released As New: Jenkins 2.282 weekly
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]
          Jeff Thompson made changes -
          Link New: This issue is duplicated by JENKINS-64992 [ JENKINS-64992 ]

            jthompson Jeff Thompson
            jthompson Jeff Thompson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: