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

TcpSlaveAgentListener prints "JNLP connection" in some messages when it is not JNLP

      The port is being used for CLI and some non-JNLP protocols outside Jenkins core. E.g. 

      • "JNLP agent listener started on TCP port {0}"
      • "Failed to accept JNLP agent connections"
      • ...
      • JNLP Port in UI

          [JENKINS-44103] TcpSlaveAgentListener prints "JNLP connection" in some messages when it is not JNLP

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-44099 [ 181725 ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Oleg Nenashev made changes -
          Labels New: newbie-friendly
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Oleg Nenashev made changes -
          Labels Original: newbie-friendly New: lts-candidate newbie-friendly
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oliver Gondža made changes -
          Labels Original: lts-candidate newbie-friendly New: 2.60.3-fixed newbie-friendly

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: