Hi John,
I just tried with a clean install again here myself to be sure, but I don't see this exception. Could you elaborate what has been changed compared to a new installation, so I can try if I can reproduce that exception myself? It looks like you're somehow getting the broker started twice in the same container. Also, it might help if you could share a bit more information about your environment (OS, JDK version) - I just tried it on Fedora and OpenJDK 1.7.0 myself. Regards, Gert Vanthienen On Thu, May 8, 2014 at 6:39 PM, John Dubchak <[email protected]> wrote: > Hi, > > I've installed and configured a new installation of SMX 5.0.0. However, > when I review the logs after startup I am seeing this error: > > org.apache.activemq.server.315a3749-8f1d-47fb-82ea-6032df4daa20 caused a > problem: Cannot start the broker > org.osgi.service.cm.ConfigurationException: null : Cannot start the broker > at > org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:110)[84:org.apache.activemq.activemq-osgi:5.9.0] > at > org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:88)[5:org.apache.felix.configadmin:1.6.0] > at > org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.provide(ConfigurationManager.java:1593)[5:org.apache.felix.configadmin:1.6.0] > at > org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceFactoryUpdate.run(ConfigurationManager.java:1536)[5:org.apache.felix.configadmin:1.6.0] > at > org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)[5:org.apache.felix.configadmin:1.6.0] > at java.lang.Thread.run(Thread.java:744)[:1.7.0_60-ea] > Caused by: javax.management.InstanceAlreadyExistsException: > org.apache.activemq:type=Broker,brokerName=amq-broker > at > com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)[:1.7.0_60-ea] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)[:1.7.0_60-ea] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)[:1.7.0_60-ea] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)[:1.7.0_60-ea] > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)[:1.7.0_60-ea] > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)[:1.7.0_60-ea] > at > org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[84:org.apache.activemq.activemq-osgi:5.9.0] > at > org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[84:org.apache.activemq.activemq-osgi:5.9.0] > at > org.apache.activemq.broker.BrokerService.startManagementContext(BrokerService.java:2401)[84:org.apache.activemq.activemq-osgi:5.9.0] > at > org.apache.activemq.broker.BrokerService.start(BrokerService.java:553)[84:org.apache.activemq.activemq-osgi:5.9.0] > at > org.apache.activemq.osgi.ActiveMQServiceFactory.updated(ActiveMQServiceFactory.java:104)[84:org.apache.activemq.activemq-osgi:5.9.0] > > I'm not entirely sure how to resolve it and all of my web searches haven't > been helpful. > > Can anyone shed some light on this? > > Thanks, > John
