[OPENAM-7076] Improve error handling or refactor usages of SystemTimerPool.getTimerPool() to handle shutdown race conditions Created: 08/Oct/15  Updated: 12/Oct/15

Status: Open
Project: OpenAM
Component/s: None
Affects Version/s: 13.0.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Ian Packer [X] (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to OPENAM-6734 Shutdown race condition between embed... Resolved
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.


Generated at Thu Apr 22 19:57:06 UTC 2021 using Jira 8.16.0#816000-sha1:a455b91378454416b49bbc88d03e653cb9815ed5.