[
https://issues.jboss.org/browse/CDI-710?page=com.atlassian.jira.plugin.sy...
]
John Ament commented on CDI-710:
--------------------------------
As the reporter notes, its to mandate that you're using the ManagedExecutor provided
by the container if none is specified by the caller. Right now in OWB, they're
relying on ForkJoinPool.commonPool() to do the work, which is an odd default choice. Weld
has a property I believe which makes sense, and of course in OWB you can override it via
properties if you need to.
Require default event ExecutorService to be managed on Java EE
--------------------------------------------------------------
Key: CDI-710
URL:
https://issues.jboss.org/browse/CDI-710
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Events
Reporter: Guillermo González de Agüero
When running on a Java EE environment, CDI should use a managed executor service by
default for asynchronous operations.
This is already required by the JAX-RS 2.1 spec
(
http://download.oracle.com/otndocs/jcp/jaxrs-2_1-pfd-spec/index.html), section 5.8:
{quote}In an environment that supports the Concurrency Utilities for Java EE [13], such
as the Java EE Full Profile, implementations MUST use ManagedExecutorService and
ManagedScheduledExecutorService, respectively. The reader is referred to the Javadoc of
ClientBuilder for more information about executor services.{quote}
Containers will presumably offer monitoring features and thread pool configuration
options for managed executor services.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)