DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20561>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20561 Limitation of availiable high ports for JK2 Summary: Limitation of availiable high ports for JK2 Product: Tomcat 4 Version: 4.1.18 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Solaris 9 Apache 2.0.46 Jakarta 4.1.18 mod_jk2 2.0.2 There seems to be a limitation on the range of ports you can use for the jk2 connector. For example port="7009" or port="17005" work in server.xml. However, high ports such as port="58009" will not. When the port is too high it seems to default to the default value (8009), even when 8009 isn't even mentioned in server.xml. Tomcat does start a listener on port 58009 and netstat sees it as in a LISTEN state. When the port is "in range" the logs are clean. from apache 2.0.46 error.log: [Fri Jun 06 11:56:47 2003] [error] channelSocket.open() connect failed 127.0.0.1 :8009 146 Connection refused [Fri Jun 06 11:56:47 2003] [error] ajp13.connect() failed ajp13:localhost:58009 [Fri Jun 06 11:56:47 2003] [error] ajp13.service() failed to connect endpoint er rno=146 Connection refused [Fri Jun 06 11:56:47 2003] [error] ajp13.service() Error forwarding ajp13:local host:58009 1 1 [Fri Jun 06 11:56:47 2003] [error] mod_jk.handler() Error connecting to tomcat 1 20000 -Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
