+1 We debated this some time ago for ActiveMQ and opted for the current functionality of allowing remote connections by default.
Bruce On Thu, May 14, 2015 at 9:32 AM, Hiram Chirino <hi...@hiramchirino.com> wrote: > I'm not sure that's a good default. ActiveMQ has traditionally > allowed remote access to it's ports. I think a localhost binding is > fine for things like management ports, but for the main service the > product gives it should be on the public ports. > > That would be like tomcat or jetty defaulting to binding it's http > ports to localhost. > > On Thu, May 14, 2015 at 11:20 AM, Justin Bertram <jbert...@apache.com> > wrote: > > IMO the broker correctly binds to localhost only and does not, by > default, allow connections from remote machines. This is a simple > security/sanity measure to prevent access to default (i.e. unsecured) > instances. > > > > The merit of this configuration is obviously up for debate, but it's > worth noting it was done on purpose. > > > > > > Justin > > > > ----- Original Message ----- > > From: "Jim Gomes" <e.se...@gmail.com> > > To: "ActiveMQ Dev" <dev@activemq.apache.org> > > Sent: Thursday, May 14, 2015 10:05:55 AM > > Subject: Re: [VOTE] Apache Artemis 1.0.0 (RC2) > > > > -1 > > > > Two reasons: > > > > 1. The default configuration of localhost for the broker does not allow > > connections from off-machine. For some reason, socket connections are > > refused from non-local clients. I had to change the broker.xml config to > > use the machine's actual IP address, and then non-local clients could > > connect. > > 2. The basic NMS OpenWire client fails to connect at all. It is getting > > unknown response IDs from the broker. I don't think the OpenWire protocol > > is being negotiated correctly. I am running with the latest NMS trunk > > version (1.8.0). > > > > > > On Wed, May 13, 2015 at 10:12 AM, Martyn Taylor <mtay...@redhat.com> > wrote: > > > >> Hello all. > >> > >> I've cut a second release candidate of Apache Artemis 1.0.0 addressing > the > >> initial RC feedback from community members. > >> > >> This is a first release of the Artemis project with protocol support for > >> AMQP, STOMP, CORE, HORNETQ and OPENWIRE. > >> > >> The release notes can be found here: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12328953 > >> > >> The binary distributions can be found here: > >> > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ > >> > >> The source archives can be found here: > >> > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1051/org/apache/activemq/apache-artemis/1.0.0/ > >> > >> The Maven repository is here: > >> > https://repository.apache.org/content/repositories/orgapacheactivemq-1051/ > >> > >> The source tag: > >> > >> > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/1.0.0 > >> > >> The project website for that version has been staged to: > >> http://people.apache.org/~martyntaylor/ > >> > >> The vote will remain open for 72 hours. > >> > >> [ ] +1 approve the release as Apache Artemis 1.0.0 > >> [ ] +0 no opinion > >> [ ] -1 disapprove (and reason why) > >> > >> Here's my (non-binding) +1 > >> > >> Regards > >> Martyn > >> > > > > -- > Hiram Chirino > Engineering | Red Hat, Inc. > hchir...@redhat.com | fusesource.com | redhat.com > skype: hiramchirino | twitter: @hiramchirino > -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' ActiveMQ in Action: http://bit.ly/2je6cQ Blog: http://bruceblog.org/ Twitter: http://twitter.com/brucesnyder
