[jboss-jira] [JBoss JIRA] (WFLY-12188) Option READ_TIMEOUT is ignored

[Flavia Rainone (Jira)]

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

Flavia Rainone updated WFLY-12188:
----------------------------------
    Priority: Minor  (was: Major)


> Option READ_TIMEOUT is ignored
> ------------------------------
>
>                 Key: WFLY-12188
>                 URL: https://issues.redhat.com/browse/WFLY-12188
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Remoting
>    Affects Versions: 17.0.0.Final
>            Reporter: Joerg Baesner
>            Assignee: Flavia Rainone
>            Priority: Minor
>
> 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}
> None of those options work.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)