Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 17.0.0.Final
    • Fix Version/s: None
    • Component/s: EJB, Remoting
    • Labels:
      None

      Description

      What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem? See:

                  <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>
      
              <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>
      

      None of those options work.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                flavia.rainone Flavia Rainone
                Reporter:
                jbaesner Joerg Baesner
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated: