Uploaded image for project: 'Confluence'
  1. Confluence
  2. CONF-18312

Despite that Confluence 3.x standalone releases are using Tomcat 6, we are still using Tomcat4 Connector

    Details

    • Type: Improvement
    • Status: Resolved
    • Resolution: Answered
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: Build
    • Labels:
      None
    • Last commented by user?:
      true

      Description

      The configuration we use in server.xml looks like this:

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

      While it's not causing any problem at the moment, I believe we should be moving to the newer version of the connector.

      Apache has removed reference to Tomcat 4's documentation from its home page, making it difficult to search information about the connector despite that they are still exist.

      We should move to Tomcat 6's connector.

        Issue Links

          Activity

          Hide
          dennis_benzinger_hybris Dennis Benzinger | hybris GmbH added a comment -

          I don't think the className attribute is used anymore. Please see the linked issue CONF-13446.

          Show
          dennis_benzinger_hybris Dennis Benzinger | hybris GmbH added a comment - I don't think the className attribute is used anymore. Please see the linked issue CONF-13446 .
          Hide
          barconati Bill Arconati 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.

          Show
          barconati Bill Arconati 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.

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                1 year, 17 weeks, 5 days ago