[jboss-jira] [JBoss JIRA] (WFLY-2534) Optimize task cancellation within BeanExpirationScheduler and SessionExpirationScheduler
[
https://issues.jboss.org/browse/WFLY-2534?page=com.atlassian.jira.plugin....
]
Paul Ferraro closed WFLY-2534.
------------------------------
Resolution: Won't Fix
Upon further review, task queue removal isn't actually an O(N) operation. The task
references an index into the queue, which gets updated as its position shifts, so queue
removal is really O(1).
Optimize task cancellation within BeanExpirationScheduler and
SessionExpirationScheduler
----------------------------------------------------------------------------------------
Key: WFLY-2534
URL: https://issues.jboss.org/browse/WFLY-2534
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 8.0.0.CR1
These implementation uses a ScheduledThreadPoolExecutor to schedule expiration of
beans/sessions, and rely heavily on task cancellation to reschedule expiration upon
access.
Unfortunately, the remove method of the BlockingQueue used by ScheduledThreadPoolExecutor
is an O(N) operation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira