• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      In Tomcat 5.5 AJP connector doc, both the minProcessors and maxProcessors are deprecated. The HTTP connector doc does not include any of the option too.
      However, the default options available in a conf/server.xml file of a Confluence standalone instance possess the following:

              <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8080" minProcessors="5"
                         maxProcessors="75"
                         enableLookups="true" redirectPort="8444" acceptCount="10" debug="0" connectionTimeout="20000"
                         useURIValidationHack="false" URIEncoding="UTF-8"/>
      

      Please consider replacing the options with:

      maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
      

            [CONFSERVER-13446] minProcessors/maxProcessors are deprecated

            Hi all, this issue has now been raised a bug here:
            https://jira.atlassian.com/browse/CONF-32970

            It is currently In Progress. Please watch that issue for updates.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Hi all, this issue has now been raised a bug here: https://jira.atlassian.com/browse/CONF-32970 It is currently In Progress. Please watch that issue for updates.

            BillA added a comment -

            Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            BillA added a comment - Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            IIUC minSpareThreads and maxSpareThreads are gone too. minSpareThreads can now be configured on the Executor element.

            Dennis Benzinger | SAP added a comment - IIUC minSpareThreads and maxSpareThreads are gone too. minSpareThreads can now be configured on the Executor element .

            Confluence 3.5.7 still has the same problem. And according to http://tomcat.apache.org/tomcat-6.0-doc/config/http.html className, debug and useURIValidationHack are old too.

            Dennis Benzinger | SAP added a comment - Confluence 3.5.7 still has the same problem. And according to http://tomcat.apache.org/tomcat-6.0-doc/config/http.html className , debug and useURIValidationHack are old too.

            Additionally, the useURIValidationHack attribute appears to be a Tomcat 4 thing as well...

            Daniel Harvey added a comment - Additionally, the useURIValidationHack attribute appears to be a Tomcat 4 thing as well...

            Daniel Harvey added a comment - - edited

            Also, the className attribute does not appear to be documented for Tomcat/6.0.14 (Confluence 3.2.1_01 standalone).

            Should be straightforward to fix this?

            Daniel Harvey added a comment - - edited Also, the className attribute does not appear to be documented for Tomcat/6.0.14 (Confluence 3.2.1_01 standalone). Should be straightforward to fix this?

              Unassigned Unassigned
              tcheah Tony Cheah Tong Nyee [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: