Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None

      Description

      In production environments, there is a need to be able to set a global default query timeout for the cfquery tag. If a query runs longer than a page timeout, Railo does not catch that as a query timeout, but a page timeout and doesn't provide any information regarding the long running query. In fact, the request will continue to run until the datasource returns with some data. This is solved by putting a timeout on the cfquery that is below the timeout of the page, but it is unreasonable in a large enterprise app that each and every cfquery have an arbitrary timeout value. It also seems unreasonable for the developers to define their own timeout (with an application/server scoped variable) and place it everywhere as needed. Is it possible to add a field in the server/web administrator for this default timeout? Maybe even an application variable similar to sessionTimeout, et al.?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                micstriit Michael Offner
                Reporter:
                jewelpengin Jonathan Larson
              • Votes:
                2 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: