Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-7076

Improve error handling or refactor usages of SystemTimerPool.getTimerPool() to handle shutdown race conditions

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 13.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Rank:
      1|hzq9jz:

      Description

      There are a number of places throughout OpenAM where SystemTimerPool.getTimerPool() is used with no error handling for a possible Runtime exception during shutdown. This can cause hangs during container shutdown or war un-deployment.

      An example of one specific place is OPENAM-6734.

      It may be worth auditing/refactoring some of these usages so that they are safer and more up to date, potentially moving away from SystemTimerPool to ScheduledExecutorService instead.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ian.packer Ian Packer [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: