[OPENAM-7076] Improve error handling or refactor usages of SystemTimerPool.getTimerPool() to handle shutdown race conditions Created: 08/Oct/15 Updated: 12/Oct/15
|Reporter:||Ian Packer [X] (Inactive)||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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
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.