[jboss-jira] [JBoss JIRA] (WFLY-1030) Add Support for Equinox ForkJoinPool

David Lloyd (JIRA) issues at jboss.org
Mon Apr 21 19:48:34 EDT 2014


     [ https://issues.jboss.org/browse/WFLY-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd updated WFLY-1030:
------------------------------

    Assignee: Eduardo Martins  (was: David Lloyd)

    
> Add Support for Equinox ForkJoinPool
> ------------------------------------
>
>                 Key: WFLY-1030
>                 URL: https://issues.jboss.org/browse/WFLY-1030
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: EE
>            Reporter: Philippe Marschall
>            Assignee: Eduardo Martins
>
> Unfortunately JSR-236 does not address Java 7 fork/join pools. This puts people how want to use fork/join pools in an awkward position, either don't use them and wait for EE 8 (four or five years) or violate the "contract" and just create them anyway.
> This presents a great opportunity for AS8 to go further than the spec and provide a {{java.util.concurrent.ForkJoinPool}} and a {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}}. This allows us to innovate and standardize at a later time in EE 8 once we gained experience.
> This should include the following features:
> * Allow the configuration of {{java.util.concurrent.ForkJoinPool}} in the server configuration. You should be able to configure the parallelism and asyncMode (see constructor arguments). Similar to {{javax.enterprise.concurrent.ManagedExecutorService}}.
> * Allow the injection of {{java.util.concurrent.ForkJoinPool}} configured in the server. Similar to {{javax.enterprise.concurrent.ManagedExecutorService}}.
> * Allow the configuration of {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}} in the server configuration, merely to match the same feature in JSR-268.
> * Allow the injection of {{java.util.concurrent.ForkJoinPool.ForkJoinWorkerThreadFactory}} configured in the server (similar to Infinispan), merely to match the same feature in JSR-268.
> * {{java.util.concurrent.ForkJoinPool}} should per default not preserve the context http://java.net/projects/concurrency-ee-spec/lists/jsr236-experts/archive/2013-02/message/10 (naming, security, transactions, class loading). Optionally you should be able to configure which contexts are preserved, this might be tough as {{ForkJoinPool}} is not designed for extensibility.
> 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.
> This issue is intended for AS8, not AS7.

--
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


More information about the jboss-jira mailing list