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

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

XMLWordPrintable

      As a follow-up to https://github.com/jenkinsci/jenkins/pull/3861 from wfollonier and to previous Pluggable Storage patches from jglick, 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.

       

          [JENKINS-56041] Ensure that InterruptedException gets propagated where it is possible in file management logic

          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.

          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.

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

              Created:
              Updated: