Anyone else having this same issue? We have 4 different environments with 4 different broker networks setup, we can't use the same multicast name for all of them, and we'd prefer not to spell out each server name in the config file, it's not very flexible. This smells like a bug.
M@ MaenXe wrote: > > I'm having an issue with my Network of Brokers configuration and an > upgrade to 5.2. The configuration we had in 5.1(which worked fine) was: > > <networkConnectors> > <networkConnector name="dev-jms-nc" > uri="multicast://dev-jms"/> > </networkConnectors> > > and > > <transportConnectors> > <transportConnector name="openwire" uri="tcp://dev-jms2:61616" > discoveryUri="multicast://dev-jms"/> > </transportConnectors> > > > Now in 5.2, it doesn't like the uri and/or discoveryUri and we get the > following errors logged and the broker does not start: > > ERROR BrokerService - Failed to start ActiveMQ JMS > Message Broker. Reason: java.net.UnknownHostException: dev-jms: dev-jms > > If I change the uri to "multicast://default" or "multicast://testing" it > seems to work just fine. Neither of those is a valid hostname, so I don't > know why it doesn't like dev-jms. > > Any suggestions? > > M@ > -- View this message in context: http://www.nabble.com/NPE%3A-java.net.UnknownHostException-after-installing-5.2%2C-same-config-as-5.1-tp21026541p21079811.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
