[jboss-jira] [JBoss JIRA] (WFLY-12188) What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
[
https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-12188:
-----------------------------------------
[~jbaesner] [~flavia.rainone] [~gtedorst] This sounds to me like a duplicate of
WFLY-11911. The READ_TIMEOUT setting in the ejb3 subsystem was cruft that had no effect.
What's the difference of the READ_TIMEOUT in ejb3 subsystem vs.
remoting subsystem
----------------------------------------------------------------------------------
Key: WFLY-12188
URL: https://issues.jboss.org/browse/WFLY-12188
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 17.0.0.Final
Reporter: Joerg Baesner
Assignee: Flavia Rainone
Priority: Major
What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_
subsystem? See:
{code}
<remote connector-ref="http-remoting-connector"
thread-pool-name="default">
<channel-creation-options>
<option name="READ_TIMEOUT"
value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
<option name="MAX_OUTBOUND_MESSAGES"
value="1234" type="remoting"/>
</channel-creation-options>
</remote>
{code}
{code}
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<endpoint/>
<http-connector name="http-remoting-connector"
connector-ref="default" security-realm="ApplicationRealm">
<!-- server-side configuration -->
<properties>
<property
name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL"
value="5000"/>
<property name="KEEP_ALIVE" value="true"/>
<property name="READ_TIMEOUT"
value="10000"/>
<property name="WRITE_TIMEOUT"
value="10000"/>
</properties>
</http-connector>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)