[
https://issues.jboss.org/browse/AS7-6573?page=com.atlassian.jira.plugin.s...
]
Philippe Marschall commented on AS7-6573:
-----------------------------------------
It would be great if AS8 went farther than the spec and provided a
{{java.util.concurrent.ForkJoinPool}} and a
{{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}}. These don't have to
(and probably shouldn't) preserve the context (see also
http://java.net/projects/concurrency-ee-spec/lists/jsr236-experts/archive...).
The advantage of this instead of manually creating a {{ForkJoinPool}} would be that it can
be configured, managed and monitored in the server (and that threads are traditionally
managed by the server).
I'm well aware that this is unspecified behaviour but so is Infinispan in AS7 and AS8
since JSR-107 again didn't make it.
Should I open a separate subtask for this?
JSR-236 Java EE 7 concurrency support parent issue
--------------------------------------------------
Key: AS7-6573
URL:
https://issues.jboss.org/browse/AS7-6573
Project: Application Server 7
Issue Type: Enhancement
Components: EE
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 8.0.0.Alpha1
Parent task for JSR-236 subtasks. Please resolve AS7-6430 only when this issue is
resolved.
--
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