the embedded broker is created in two different ways and as such is quite different. With broker:(...) you get all the defaults. With broker-config.xml the values are non default and come from the xml. for instance, there is no mbean server created in the broker-config.xml case so there is nothing listening on rmi
To see how the webconsole is configured (via properties) peek at: http://activemq.apache.org/web-console.html you may want to override webconsole.jmx.url to point to the glassfish mbean server. Alternatively, reference your own xml config and create an mbean server. On 17 April 2013 15:04, javadude <[email protected]> wrote: > Using xbean like > BrokerXmlConfig = > xbean:file:/opt/app-server/glassfish/domains/mydomain/applications/activemq-rar-5.7.0/broker-config.xml > (which works fine for the settings) > > but when I open the webconsole > (http://www.mydomain.net:8080/activemq-web-console-5.7.0/) I get this in > the server.log > > /java.io.IOException: java.lang.RuntimeException: java.io.IOException: > Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException > [Root exception is java.rmi.ConnectException: Connection refused to host: > 0.0.0.0; nested exception is: / > > > the webconsole will work only with > BrokerXmlConfig = broker:(tcp://0.0.0.0:61616) > > Thanks > Sven > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/BrokerXmlConfig-setting-conflicts-with-external-config-for-embedded-setup-tp4665983p4665992.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
