This is a known issue, which was fixed, maybe in 4.1.14. The connector wasn't using the port value in server.xml, for some fairly complicated reasons. (eventually it should get that value from jk2.properties, the same file that mod_jk2 will be reading, but the architecture to support that isn't completely in place). The immediate patch made the coyote connector use all of the settings that are found in server.xml.
Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> [EMAIL PROTECTED] 11/18/02 5:43:57 PM >>> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8004" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" useURIValidationHack="false" protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/> Even with the above configuration, this connector tries to start up on port 8009. Anyone know why? Brandon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
