We run Jenkins 2.107.2 / 2.107.3 on Debian Linux server and >50 agents with linux, Win7, Win10 connected via JNLP.
Sometimes we use the possibility to cancel running jobs interactively without problems. When upgrading the Jenkins server to 2.150.3 (and 2.176.2 and more recent releases) and the agent jars appropriately, we get trouble. After canceling a job execution, the agent running the job looses the connection to the master. All agent are connected via JNLP. Anyone else observing similar problems? I do not believe that we are the only users of JNLP, but do not understand why nobody else reports such a problem. At least I find no similar reports. Any ideas where to search, how to work around or solve the issue? Its blocking us from upgrading Jenkins. Thanks and Best Regards, Jürgen -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com.
