[ https://issues.apache.org/jira/browse/GERONIMO-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang resolved GERONIMO-6110. ------------------------------------- Resolution: Fixed Fix at revision: 1158486. > On 3.0 we don't register the 61616 port and the IP address for the server > socket is not correct. > ------------------------------------------------------------------------------------------------ > > Key: GERONIMO-6110 > URL: https://issues.apache.org/jira/browse/GERONIMO-6110 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ > Affects Versions: 3.0 > Reporter: Rex Wang > Assignee: Han Hong Fang > Fix For: 3.0 > > > Kevan report following in GERONIMO-5987, I think it is better to open a > separate jira to track this problem. > Rex, since this may be related - two things about ActiveMQ that I noticed, > yesterday. If you don't feel these are related enough, let's get a separate > Jira to track these. > 1. we're not currently displaying the ActiveMQ listening port during > server startup. > 2. the server socket is listening on 127.0.0.1, not 0.0.0.0 > Here's output for a 2.1.x server start: > Listening on Ports: > 1050 0.0.0.0 CORBA Naming Service > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 2001 0.0.0.0 OpenEJB ORB Adapter > 4201 0.0.0.0 OpenEJB Daemon > 6882 0.0.0.0 OpenEJB ORB Adapter > 8009 0.0.0.0 Tomcat Connector AJP AJP > 8080 0.0.0.0 Tomcat Connector HTTP BIO HTTP > 8443 0.0.0.0 Tomcat Connector HTTPS BIO HTTPS > 9998 0.0.0.0 JMX Secure Remoting Connector > 9999 0.0.0.0 JMX Remoting Connector > 61613 0.0.0.0 ActiveMQ Transport Connector > 61616 0.0.0.0 ActiveMQ Transport Connector > We no longer start the Stomp connector (61613) by default. Which is good I > think. However, on 3.0 we don't register the 61616 port and the IP address > for the server socket is not correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira