DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40537>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40537 Summary: [PATCH] Allow admin to configure different IP address for SHUTDOWN Product: Tomcat 5 Version: Unknown Platform: All OS/Version: All Status: NEW Keywords: PatchAvailable Severity: enhancement Priority: P4 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] This is a pretty unique case, but we have over forty instances of Tomcat running on any given machine, each bound to their own IP addresses. The problem is that the listener for SHUTDOWN always binds to 127.0.0.1. Although the port number is configurable, it gets a little unruly to manage that many. This patch expands on the ability to set the port, by allowing the IP address to be configured as well in server.xml. I am aware of the security implications, that something other than localhost may be accessible from other locations, but I argue that it's really up to the admin to take care of that with good firewall rules. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
