[
https://issues.apache.org/jira/browse/WICKET-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719475#comment-17719475
]
ASF GitHub Bot commented on WICKET-7052:
----------------------------------------
martin-g commented on PR #588:
URL: https://github.com/apache/wicket/pull/588#issuecomment-1535228229
Thank you, @reckart !
> Interrupting a task should not be logged as an error
> ----------------------------------------------------
>
> Key: WICKET-7052
> URL: https://issues.apache.org/jira/browse/WICKET-7052
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Reporter: Richard Eckart de Castilho
> Assignee: Martin Tzvetanov Grigorov
> Priority: Minor
> Fix For: 10.0.0, 9.14.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
