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

[Brian Stansberry (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785046#comment-13785046 ] 

Brian Stansberry commented on WFLY-12188:
-----------------------------------------

[~flavia.rainone] We'd discussed this a bit elsewhere; I'm saying the same here.

+1 for documentation.

If setting those options on the http-connector resource ever worked, let me know.

If configuring the options on the http-connector resource isn't really useful or isn't achievable at a cost that's acceptable, then the resource should be marked as deprecated. That will result in a message in the server log if they are configured. And then in a future release we can remove the resource.

Neither the need for docs nor the task to deprecate the resource are Blocker priority.

> Option READ_TIMEOUT is ignored
> ------------------------------
>
>                 Key: WFLY-12188
>                 URL: https://issues.jboss.org/browse/WFLY-12188
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Remoting
>    Affects Versions: 17.0.0.Final
>            Reporter: Joerg Baesner
>            Assignee: Flavia Rainone
>            Priority: Blocker
>              Labels: blocker-WF18
>
> 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.5#713005)