[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool the link to jetty issue is public. the verification was a private repo Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2068.1583096880179%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated JENKINS-60821 Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2065.1583096760313%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title Manuel Recena Soto commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool The links provided in the issue description are broken. I assume they are private links. According to the CHANGELOG, we are able to update the status of this issue. It is already released. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2061.1583095200205%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title Oleg Nenashev commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool I will cut the Jetty release Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.7024.1580167200140%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool Jenkins test harness has not been released yet but happy to close as it's been merged, just not sure on the process for jth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.7022.1580166780189%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool James Nord Winstone fix was shipped in 2.218. Do we need to keep this issue open? Change By: Oleg Nenashev Released As: Jenkins 2.218 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.6992.1580165160155%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated JENKINS-60821 Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.4500.1579798860272%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord assigned an issue to Unassigned Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.4501.1579798860347%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong.Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/ 9 96 ] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe]We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins are safe * winstone ✔ * maven-hpi-plugin (run mojoe etc) ✔ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool maven-hpi-plugin seems unaffected winstone allows for configuration of the acceptors and selectors and the max # threads (which by default uses Jetty defaults) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2962.1579548780110%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong.Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe]We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkinsare safe * winstone ✔ * maven-hpi-plugin (run mojoe etc) ✔ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492] which was created to report the failure to process requests we have been told that our code is wrong.Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe]We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) ✔ * make sure other uses of Jetty in Jenkins (winsone, RunMojo ( * winstone * maven- hpi- pluin plugin (run mojoe etc ) ) are not affected also. ✔ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492 ) ] which was created to report the failure to process requests we have been told that our code is wrong.Jesse Glick verified the fix in [cloudbees-workflow-template-plugin#9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9] [commit 0c4eb98d|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe]We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord commented on JENKINS-60821 Re: Check and update any Jetty code with custom threadpool removing the thread naming means the threadpool uses threads starting with "qtp" rather than "Jetty Thread Pool" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2953.1579544280049%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord updated an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Change By: James Nord As per [Jetty Issue#4492|https://github.com/eclipse/jetty.project/issues/4492)] which was created to report the failure to process requests we have been told that our code is wrong.Jesse Glick verified the fix in [ https://github.com/ cloudbees /cloudbees -workflow-template-plugin /pull/ # 9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/ 96 9 ] 6 [ (https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe commit 0c4eb98d |https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe ) ]We need to * see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) * make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. slack: [https://cloudbees.slack.com/archives/CBXU9VCGL/p1579285074024500?thread_ts=1579193579.070300=CBXU9VCGL] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord started work on JENKINS-60821 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204164.1579518587000.2593.1579518960206%40Atlassian.JIRA.
[JIRA] (JENKINS-60821) Check and update any Jetty code with custom threadpool
Title: Message Title James Nord created an issue Jenkins / JENKINS-60821 Check and update any Jetty code with custom threadpool Issue Type: Improvement Assignee: James Nord Components: jenkins-test-harness, maven-hpi-plugin, winstone-jetty Created: 2020-01-20 11:09 Priority: Minor Reporter: James Nord As per Jetty Issue#4492 which was created to report the failure to process requests we have been told that our code is wrong. Jesse Glick verified the fix in [ https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/9|https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96]6 (https://github.com/cloudbees/cloudbees-workflow-template-plugin/pull/96/commits/0c4eb98d94008760d077dbc36d5e33e5bdb398fe We need to see if we can remove the custom thread pools from `jenkins-test-harness` (it only is used to set the name of the Thread) make sure other uses of Jetty in Jenkins (winsone, RunMojo (hpi-pluin)) are not affected also. slack: https://cloudbees.slack.com/archives/CBXU9VCGL/p1579285074024500?thread_ts=1579193579.070300=CBXU9VCGL
