[SERVER-58025] TimestampMonitor listener loop crashes on non-interruption exception. Created: 23/Jun/21 Updated: 29/Oct/23 Resolved: 17/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Yuhong Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2021-07-26, Execution Team 2021-08-09, Execution Team 2021-08-23 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
The TimestampMonitor currently checks and reports Interruption as it is processing its listeners. We have observed in our CI system that the server crashes when we have an exception type that is not handled by the current PeriodicJob task. It would be useful to include an additional exception handling loop for non-Interruption types and handle these exceptions appropriately. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 16/Aug/21 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}Message: |
| Comment by Benety Goh [ 24/Jun/21 ] |
|
We do not want to bury the non-interruption exception in this loop. The first step is to log the exception and rethrow. We would still abort the server operation. |