[
https://issues.jboss.org/browse/WFLY-8387?page=com.atlassian.jira.plugin....
]
Stuart Douglas moved JBEAP-9610 to WFLY-8387:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8387 (was: JBEAP-9610)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Affects Version/s: (was: 7.1.0.DR13)
Affects Testing: (was: Regression)
EJB remote invocations always execute in IO worker even when not
supposed to
----------------------------------------------------------------------------
Key: WFLY-8387
URL:
https://issues.jboss.org/browse/WFLY-8387
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Priority: Blocker
When you configure EJB3 subsystem so that remote invocations should be executed in thread
pools of EJB3 subsystem instead of IO worker threads:
{noformat}
/subsystem=ejb3/service=remote:write-attribute(name=execute-in-worker,value=false)
{noformat}
This seems to have no effect and invocations are still executed in IO worker threads.
This is a regression, in EAP 7.0 it works correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)