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=21564>. 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=21564 CoyoteConnector binds to all hosts even when a specific host (incorrect) is specified Summary: CoyoteConnector binds to all hosts even when a specific host (incorrect) is specified Product: Tomcat 4 Version: 4.1.24 Platform: All OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CoyoteConnector correctly handles cases where the server socket port is in use. This was a blocking issue for us with the (now deprecated) Http1.1 connector. However we have now found that it can have a similar problem, but earlier on during configuration. IntrospectionUtils is used by CoyoteConnector to call Http11Protocol.setAddress(InetAddress). However the IntrospectionUtils logic seems too leniant. If it encounters an error then it prints a debug statement but continues as if there was no problem. Meaning that there is no host specified and it binds to all hosts. The problem for us is a typo in the host name, and IntrospectionUtils swallows the exception. IntrospectionUtils: Unable to resolve host name:wappull-sna-2 I can't understand why IntrospectionUtils is so leniant in the following cases: - the required argument is an InetAddress and host is invalid (our problem) - the required argument is a number and the number is invalid - the method is not found. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
