Cancel Job aborts Agent Connection (JNLP)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Cancel Job aborts Agent Connection (JNLP)

JuBo

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Cancel Job aborts Agent Connection (JNLP)

Mark Waite-2
Did you upgrade the agent.jar that is used on your Jenkins agents?  Most connections launched from an external process (JNLP) will keep a local copy of the agent.jar file.  That local copy may be outdated and need an update.  Especially in a jump of 50 or more versions.  That is a one year jump in Jenkins releases, likely there have been remoting changes in that time.

The VersionColumn plugin can add a check to your Jenkins master which will complain when agent jar files are outdated.

On Wed, Mar 18, 2020 at 2:29 AM JuBo <[hidden email]> wrote:

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFfx0QsnwA_8fVL-30qv5iavVq22ZFKwDC1kPsYdZgmhg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Cancel Job aborts Agent Connection (JNLP)

JuBo
Yes, we upgraded it. I know how to check this in the UI as well as scripted on the master.

We tested this not only one year later but with different intermediate releases.
I've also created a bug report last year in summer (https://issues.jenkins-ci.org/browse/JENKINS-58764), but it has been ignored.

Thanks for your feedback. Any further hint it very appreciated!

Best Regards,
 Jürgen

On Wednesday, March 18, 2020 at 6:23:30 PM UTC+1, Mark Waite wrote:
Did you upgrade the agent.jar that is used on your Jenkins agents?  Most connections launched from an external process (JNLP) will keep a local copy of the agent.jar file.  That local copy may be outdated and need an update.  Especially in a jump of 50 or more versions.  That is a one year jump in Jenkins releases, likely there have been remoting changes in that time.

The VersionColumn plugin can add a check to your Jenkins master which will complain when agent jar files are outdated.

On Wed, Mar 18, 2020 at 2:29 AM JuBo <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="kkbCJ1EkBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">btc...@...> wrote:

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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="kkbCJ1EkBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkins...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-users/56664cce-9c44-4d6a-a32a-ab449bce7a86%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/478f0edd-e6ba-4bad-a68a-0b5ab10677dd%40googlegroups.com.