[
https://issues.apache.org/jira/browse/JAMES-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117243#comment-17117243
]
Benoit Tellier commented on JAMES-3172:
---------------------------------------
https://github.com/linagora/james-project/pull/3384
The uses of signals can not be expected to be immediate. Thus
theWorkerShouldCancelAnInProgressTask test was failing as the
cancellation could be repeated after the mock check, eventually
failing the test.
This effectively solves the instability noticed on
theWorkerShouldCancelAnInProgressTask
> Cancel a task doesn't seem to really work
> -----------------------------------------
>
> Key: JAMES-3172
> URL: https://issues.apache.org/jira/browse/JAMES-3172
> Project: James Server
> Issue Type: Bug
> Reporter: René Cordier
> Priority: Major
>
> Test done with a james-rabbitmq-project docker image (which I believe is
> using the Distributed Task Manager)
>
> Launch a task a on provisionned James and try to cancel it, and keep looking
> at the logs in James...
>
> For example, I ran the recompute current quota task :
> {code:java}
> curl -XPOST 'http://[JAMES_ADDRESS]/quota/users?task=RecomputeCurrentQuotas'
> {code}
>
> Then I cancel it
> {code:java}
> curl -XDELETE 'http://james-charge-01:8000/tasks/[TASK_NUMBER]
> {code}
> By checking the status of the task, I can see that the task has been
> cancelled... However, if I look at the logs on James at the same time, I
> could see INFO logs about quotas being still recomputed for users.
> It looks like to me even if the task got cancelled with the task scheduler,
> it's still running somehow... Which should not happen
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
