[
https://issues.jboss.org/browse/WFCORE-3868?page=com.atlassian.jira.plugi...
]
Yeray Borges commented on WFCORE-3868:
--------------------------------------
Yes, it is specific to domain mode, standalone server is shutting down without any
problems. It is an issue with the graceful shutdown using 0 as timeout and when an
activity is not suspended at all because the managed executor is creating a task from an
existing task.
Domain mode shutdown of EE executor service with :stop() or
:stop(timeout=0) command doesn't work
-------------------------------------------------------------------------------------------------
Key: WFCORE-3868
URL:
https://issues.jboss.org/browse/WFCORE-3868
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 5.0.0.Beta4
Reporter: Yeray Borges
Assignee: Yeray Borges
Attachments: ExecutorServiceShutdownReproducer.war
EAP's EE-Concurrency Managed Executor Service is expected to skip the tasks that are
pending in its execution queue upon server shutdown as [documented here
|https://docs.jboss.org/author/display/WFLY/Suspend%2C+Resume+and+Graceful+shutdown]
This is necessary to cope with scenario where a polling-type task is re-scheduling a new
instance of itself just before exiting (so that there is always one task polling - pattern
used e.g. by Spring message listeners
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)