[
https://issues.jboss.org/browse/JGRP-1474?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1474:
--------------------------------
The workaround is not to use the thread pools created by the AS, but make JGroups use its
own pools.
TimeScheduler: add method to inject a thread pool
-------------------------------------------------
Key: JGRP-1474
URL:
https://issues.jboss.org/browse/JGRP-1474
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2
JBossAS has its own implementation of TimeScheduler (causing problems, see [1]). However,
it would be much better to allow the AS to use the configured TimeScheduler implementation
(e.g. TimeScheduler2, HashTimingWheel or DefaultTimeScheduler) and inject the thread pool
configured by the AS into this implementation.
This requires DefaultTimeScheduler to delegate to a thread pool rather than extending
ScheduledThreadPoolExecutor though.
[1]
https://issues.jboss.org/browse/JBAS-9486
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira