XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 6.4.0.GA
    • Documentation

    Description

      Nodetimeout description in the administration and configuration guide (https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/pdf/Administration_and_Configuration_Guide/JBoss_Enterprise_Application_Platform-6.4-Administration_and_Configuration_Guide-en-US.pdf) is defined twice and the description are contradictory.

      First description:
      Node Timeout :Timeout (in seconds) for proxy connections to a worker. That is the time mod_cluster will wait for the back-end response before returning error. That corresponds to timeout in the mod_proxy documentation. A value of -1 indicates no timeout. Note that mod_cluster always uses a cping/cpong before forwarding a request and the connectiontimeout value used by mod_cluster is the ping value.

      Second description :
      Node Timeout : How long, in seconds, to wait for an available process from the external Web server to process a request. Defaults to -1, which means that mod_cluster waits indefinitely for the httpd worker to process the request.

      Second description states "Defaults to -1, which means that mod_cluster waits indefinitely for the httpd worker to process the request" , which is not the case.

      And in addition to it TTL description has "When nodeTimeout is not defined the ProxyTimeout directive Proxy is used. If ProxyTimeout is not defined the server timeout Timeout is used. This defaults to 300 seconds. nodeTimeout, ProxyTimeout, and Timeout are set at the socket level.". It should be part of Node Timeout.

      Attachments

        Activity

          People

            rhn-support-sshashan sujay shashank (Inactive)
            rhn-support-sshashan sujay shashank (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: