[ http://issues.apache.org/jira/browse/GERONIMO-930?page=comments#action_12320369 ]
Jeff Genender commented on GERONIMO-930: ---------------------------------------- 0.0.0.0 needs to be the default for all listeners. Its not a server, its an address, or the generic listener for all IP addresses. localhost is not what should be listened on, it is truly the server host name. This can be used for the true meaning of a host. We have to be careful which is applied to what. I recommend we have a 0.0.0.0 that is used for listeners, and call it PlanListenerAddress, and leave PlanServerHostname as is. There are really 2 seperate components. A perfect example is Tomcat, where the Host object requires the PlanServerHostname (localhost) and the Connector objects require PlanListenerAddress (0.0.0.0). However, I have noticed a bug, and I am not sure if it belongs in this JIRA issue, where I have 0.0.0.0 set in the GBeans, and upon server restart (second run), it changes itself over to 127.0.0.1. This is a problem. > Default host for open sockets (at least web ones) should be default host > 0.0.0.0 and not localhost > -------------------------------------------------------------------------------------------------- > > Key: GERONIMO-930 > URL: http://issues.apache.org/jira/browse/GERONIMO-930 > Project: Geronimo > Type: Bug > Components: connector > Versions: 1.0-M5 > Environment: All > Reporter: Matt Hogstrom > > These are the current ports Geronimo is listening on by default: > Listening on Ports: > 1099 0.0.0.0 RMI Naming > 1527 127.0.0.1 Derby Connector > 4201 127.0.0.1 OpenEJB Connector EJB > 8080 127.0.0.1 Jetty Connector HTTP > 8443 127.0.0.1 Jetty Connector HTTPS > 61616 0.0.0.0 ActiveMQ Message Broker Connector > Unfortunately, to do handle any external traffic Jetty has to be reconfigured > to listen on 0.0.0.0 or be bound to a specific interface. I propse that the > default for Jetty be changed to 0.0.0.0 for both HTTP and HTTPS. I also > think Derby should be open as well so it could be administrered remotely but > I'm less passionate about that one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
