[WICKET-7052] Interrupting a task should not be logged as an error

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 10.0.0-M1, 9.14.0
• Component/s: wicket-core
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Richard Eckart de Castilho
• Created: 01/May/23 16:09
• Updated: 04/May/23 18:33
• Resolved: 04/May/23 18:32

Description

An interrupt can be used to wake a sleeping task so it can check if it has been stopped. Since this is not an uncommon scenario, it should not be logged as an error.

Consider for example the ModificationWatcher. On shutdown, its destroy method is called which may interrupt() the watcher task. Calling Task.interrupt() will set the stop flag in the task and then interrupt the task thread. If this happens while the task is sleeping, it should not cause an error to be logged.

Issue Links

• links to: GitHub Pull Request #588