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

Ensure that InterruptedException gets propagated where it is possible in file management logic

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      As a follow-up to https://github.com/jenkinsci/jenkins/pull/3861 from Wadeck Follonier and to previous Pluggable Storage patches from Jesse Glick, I would like to revisit usage of InterruptedException. Currently this exception type gets suppressed in many use-cases around file management, and it may lead to improper Jenkins restarts and termination in some cases when threads do not get properly interrupted.

       

        Attachments

          Activity

          Hide
          Permalink
          jglick Jesse Glick added a comment -

          By the way this post is quite thought-provoking. Certainly it is relevant to the API designs used in Remoting, though to a much lesser extent it is significant for local file operations. One of his points is that edge-triggered models such as Java’s interruption are difficult to use correctly, especially across libraries. Not sure there is much we can do about it without intrusive changes.

          Show
          jglick Jesse Glick added a comment - By the way this post is quite thought-provoking. Certainly it is relevant to the API designs used in Remoting, though to a much lesser extent it is significant for local file operations. One of his points is that edge-triggered models such as Java’s interruption are difficult to use correctly, especially across libraries. Not sure there is much we can do about it without intrusive changes.

            People

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

              Dates

              Created:
              Updated: