[JENKINS-53239] Use default Jetty QueuedThreadPool

        Olivier Lamy added a comment - - edited

        The current home made BoundedExecutorService is creating few issues (see linked jira).

        pr ready: https://github.com/jenkinsci/winstone/pull/54

        TBH my preferred solution is simply to get RID of the BoundedExecutorService class

        Olivier Lamy added a comment - - edited The current home made  BoundedExecutorService is creating few issues (see linked jira). pr ready: https://github.com/jenkinsci/winstone/pull/54 TBH my preferred solution is simply to get RID of the BoundedExecutorService class

        Oleg Nenashev added a comment -

        +1

        Oleg Nenashev added a comment - +1

        Mike Scholze added a comment -

        +1

        Mike Scholze added a comment - +1

        Eric Boehm added a comment -

        +1

        Eric Boehm added a comment - +1

        Olivier Lamy added a comment -

        Olivier Lamy added a comment - https://github.com/jenkinsci/winstone/commit/74775cc02ef92feaf247e45a32b193e45800805a

        Vlad added a comment -

        Can you merge the fix into the next LTS release? LTS 2.138.x? Otherwise people using LTS releases only would have to wait next 12 weeks for the fix.

        Vlad added a comment - Can you merge the fix into the next LTS release? LTS 2.138.x? Otherwise people using LTS releases only would have to wait next 12 weeks for the fix.

        Oleg Nenashev added a comment -

        I have marked it as LTS candidate. I am not 100% sure it is backportable, but there is a good community feedback so far.

        CC olivergondza

         

        Oleg Nenashev added a comment - I have marked it as LTS candidate. I am not 100% sure it is backportable, but there is a good community feedback so far. CC olivergondza  

        Vlad added a comment -

        We have tested winstone.jar from the Pull request on a build server with 80 CPU cores and can confirm, the issue was resolved.

        Vlad added a comment - We have tested winstone.jar from the Pull request on a build server with 80 CPU cores and can confirm, the issue was resolved.

        Yes, please backport this, we need it as well! Thanks

        Carsten Pfeiffer added a comment - Yes, please backport this, we need it as well! Thanks

        It would be great to have it back-ported to LTS 2.121.* from where it is started to occur, to have valid upgrade path for LTS releases

        Alexey Grigorov added a comment - It would be great to have it back-ported to LTS 2.121.* from where it is started to occur, to have valid upgrade path for LTS releases

          olamy Olivier Lamy
          olamy Olivier Lamy
          Votes:
          2 Vote for this issue
          Watchers:
          11 Start watching this issue

            Created:
            Updated:
            Resolved: