Bug 49031

Summary: The server.xml in the fresh installed Tomcat 64bit for Windows 2003 Server contains invalid connector specification
Product: Tomcat 6 Reporter: Artur Linhart <Artur.Linhart>
Component: Native:PackagingAssignee: Tomcat Developers Mailing List <dev>
Status: RESOLVED INVALID    
Severity: normal    
Priority: P2    
Version: 6.0.26   
Target Milestone: default   
Hardware: PC   
OS: Windows XP   

Description Artur Linhart 2010-03-31 12:39:37 UTC
The default configuration in the windows installer for Windows 2003 64 bit contains the invalid server.xml configuration. It contains twice the connector allocating the port 9080:

<Service name="Catalina">
  
    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" 
        maxThreads="150" minSpareThreads="4"/>
    -->
    
    
    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    -->
    <Connector port="9080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="9443" />
    <!-- A "Connector" using the shared thread pool-->
   
    <Connector executor="tomcatThreadPool"
               port="9080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="9443" />
               
... etc.

So it leads always to the error by the start of the service. Togenther with the bug 49030 then all other connectors defined below, like AJP etc. are not initialized...
Comment 1 Mark Thomas 2010-03-31 12:54:51 UTC
A clean Tomcat installation does not configure any connectors on port 9080.

Please use the users mailing list if you require further assistance with this issue.
Comment 2 Artur Linhart 2010-03-31 13:08:05 UTC
Yes, soryy, it was invalid request, based on invalid data. My apologies...