Unable to Configure the ActiveMQ Web Console and a Broker in the same Fabric Child Container
Issue
- When trying to configure a broker and the ActiveMQ Web Console in the same Fabric child container the following error occurs:
2013-07-31 08:16:23,521 | INFO | .fabric.server]) | ActiveMQServiceFactory | q.fabric.ActiveMQServiceFactory$ 52 | 228 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker tcs02s-mq01 is waiting to become the master
2013-07-31 08:16:23,531 | INFO | .fabric.server]) | ActiveMQServiceFactory | q.fabric.ActiveMQServiceFactory$ 52 | 228 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker tcs02s-mq01 added to pool default.
2013-07-31 08:16:23,548 | INFO | Executor: 1 | WebXmlObserver | nder.war.internal.WebXmlObserver 120 | 236 - org.ops4j.pax.web.pax-web-extender-war - 1.1.11 | Using [activemqweb] as web application context name
2013-07-31 08:16:23,552 | INFO | Executor: 1 | WebXmlObserver | nder.war.internal.WebXmlObserver 141 | 236 - org.ops4j.pax.web.pax-web-extender-war - 1.1.11 | Using [] as web application root path
2013-07-31 08:16:23,588 | INFO | agent-1-thread-1 | DeploymentAgent | rce.fabric.agent.DeploymentAgent 760 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | activemq-karaf / 5.8.0.redhat-60024
2013-07-31 08:16:23,621 | INFO | agent-1-thread-1 | DeploymentAgent | rce.fabric.agent.DeploymentAgent 760 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | org.springframework.context.support / 3.1.3.RELEASE
2013-07-31 08:16:23,625 | INFO | agent-1-thread-1 | DeploymentAgent | rce.fabric.agent.DeploymentAgent 760 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | org.ops4j.pax.web.pax-web-jetty / 1.1.11
2013-07-31 08:16:23,636 | INFO | agent-1-thread-1 | DeploymentAgent | rce.fabric.agent.DeploymentAgent 772 | 4 - org.ops4j.pax.logging.pax-logging-api - 1.7.0 | Done.
2013-07-31 08:16:23,663 | INFO | ad-8-EventThread | ActiveMQServiceFactory | q.fabric.ActiveMQServiceFactory$ 52 | 228 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker tcs02s-mq01 is now the master, starting the broker.
2013-07-31 08:16:23,676 | INFO | b Runtime worker | Server | org.eclipse.jetty.server.Server 266 | 224 - org.eclipse.jetty.util - 7.6.7.v20120910 | jetty-7.6.7.v20120910
2013-07-31 08:16:23,683 | INFO | ker: tcs02s-mq01 | ActiveMQServiceFactory | q.fabric.ActiveMQServiceFactory$ 52 | 228 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Broker tcs02s-mq01 failed to start. Will try again in 10 seconds
2013-07-31 08:16:23,684 | INFO | ker: tcs02s-mq01 | ActiveMQServiceFactory | y$ClusteredConfiguration$$anon$3 325 | 228 - org.jboss.amq.mq-fabric - 6.0.0.redhat-024 | Exception on start: java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) previously initiated loading for a different type with name "org/springframework/core/io/Resource"
java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoaderJava5) previously initiated loading for a different type with name "org/springframework/core/io/Resource"
at org.fusesource.mq.fabric.ActiveMQServiceFactory$$anon$1.<init>(ActiveMQServiceFactory.scala:83)[228:org.jboss.amq.mq-fabric:6.0.0.redhat-024]
at org.fusesource.mq.fabric.ActiveMQServiceFactory$.createBroker(ActiveMQServiceFactory.scala:83)[228:org.jboss.amq.mq-fabric:6.0.0.redhat-024]
at org.fusesource.mq.fabric.ActiveMQServiceFactory$ClusteredConfiguration$$anon$3.run(ActiveMQServiceFactory.scala:305)[228:org.jboss.amq.mq-fabric:6.0.0.redhat-024]
2013-07-31 08:16:23,701 | INFO | b Runtime worker | JettyServerImpl | e.jetty.internal.JettyServerImpl 132 | 246 - org.ops4j.pax.web.pax-web-jetty - 1.1.11 | Pax Web available at [0.0.0.0]:[8080]
2013-07-31 08:16:23,707 | INFO | b Runtime worker | AbstractConnector | e.jetty.server.AbstractConnector 338 | 224 - org.eclipse.jetty.util - 7.6.7.v20120910 | Started NIOSocketConnectorWrapper@0.0.0.0:8080
2013-07-31 08:16:23,709 | INFO | -1.1.11-thread-1 | HttpServiceFactoryImpl | .internal.HttpServiceFactoryImpl 33 | 225 - org.ops4j.pax.web.pax-web-runtime - 1.1.11 | Binding bundle: [org.jboss.amq.mq-web-console [217]] to http service
2013-07-31 08:16:23,756 | WARN | b Runtime worker | AbstractLifeCycle | util.component.AbstractLifeCycle 204 | 224 - org.eclipse.jetty.util - 7.6.7.v20120910 | FAILED org.eclipse.jetty.security.ConstraintSecurityHandler@5472b93e: java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.BasicAuthenticator@4f0ecbfe in org.eclipse.jetty.security.ConstraintSecurityHandler@5472b93e
java.lang.IllegalStateException: No LoginService for org.eclipse.jetty.security.authentication.BasicAuthenticator@4f0ecbfe in org.eclipse.jetty.security.ConstraintSecurityHandler@5472b93e
at org.eclipse.jetty.security.authentication.LoginAuthenticator.setConfiguration(LoginAuthenticator.java:45)[238:org.eclipse.jetty.security:7.6.7.v20120910]
at org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:376)[238:org.eclipse.jetty.security:7.6.7.v20120910]
at org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:233)[238:org.eclipse.jetty.security:7.6.7.v20120910]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)[224:org.eclipse.jetty.util:7.6.7.v20120910]
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)[229:org.eclipse.jetty.server:7.6.7.v20120910]
at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:115)[229:org.eclipse.jetty.server:7.6.7.v20120910]
at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:120)[229:org.eclipse.jetty.server:7.6.7.v20120910]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)[224:org.eclipse.jetty.util:7.6.7.v20120910]
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)[229:org.eclipse.jetty.server:7.6.7.v20120910]
Environment
- Red hat JBoss Fuse
- 6.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.