[
https://issues.jboss.org/browse/WFLY-3695?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated WFLY-3695:
-------------------------------
Description: The ScheduledExecutorService employed by the SessionExpirationScheduler
uses shutdown() to shutdown the thread pool - however, unless we explicitly
setExecuteExistingDelayedTasksAfterShutdownPolicy(false), all scheduled tasks will attempt
to execute after shutdown! (was: These thread pools currently shutdown via
ExecutorService.shutdownNow() but leave active threads. Shutdown is also a blocking
operation, so Service.stop(...) should be asynchronous.)
Distributed web session expiration ScheduledExecutorService leaks
threads on undeploy
-------------------------------------------------------------------------------------
Key: WFLY-3695
URL:
https://issues.jboss.org/browse/WFLY-3695
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 8.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 8.2.0.CR1, 9.0.0.Beta1
The ScheduledExecutorService employed by the SessionExpirationScheduler uses shutdown()
to shutdown the thread pool - however, unless we explicitly
setExecuteExistingDelayedTasksAfterShutdownPolicy(false), all scheduled tasks will attempt
to execute after shutdown!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)